500 MB Nyheder Direkte fra Internet 5/500 MB nyheder direkte fra internet CD 5.iso/start/zipped/dos/novell/nips21.exe/NWIP3/BOOKS/NFSCLENU/NFSCLENU

Text File | 1994-12-21 | 118KB | 1,867 lines

<!DOCTYPE BOOK SYSTEM "/dtd/docbook.dtd" [
<!ENTITY % localentities SYSTEM "/dtd/novlents">
%localentities;
]>

<BOOK><TITLE>NetWare/IP Client Guide</TITLE>
<BOOKINFO>
<BOOKBIBLIO><TITLE>NetWare/IP Client Guide</TITLE>
<AUTHORGROUP><CORPAUTHOR>Novell, Inc.</CORPAUTHOR></AUTHORGROUP></BOOKBIBLIO>
<LEGALNOTICE>
<TITLE>Disclaimer</TITLE>

<PARA>Novell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.</PARA>

<PARA>Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.</PARA>

</LEGALNOTICE>

<LEGALNOTICE>
<TITLE>Trademarks</TITLE>

<PARA>Btrieve, DR DOS, EXOS, LANalyzer, LAN WorkPlace, NetWare,
OnLAN/MAC, OnLAN/PC, Script Director, Novell, the NetWare Logotype,
and the N design are registered trademarks of Novell, Inc.</PARA>

<PARA>Advanced NetWare, Boot Support Module, BSM, Business Smarts, DOS
Protocol Mode Services, DPMS, ElectroText, FirstMail, GEM/3, Hardware
Specific Module, Host Presenter, Hot Fix, HSM, Internetwork Packet
Exchange, IPX, LAN Service, LAN WorkGroup, Link Support Layer, LSL,
Media Support Module, Mobile WorkPlace, MSM, Multiple Link Interface,
MLI, Multiple Link Interface Driver, MLID, Multiple Protocol
Interface, MPI, NetWare 3, NetWare 4, NetWare Access Server, NetWare
Access Services, NetWare Asynchronous Communication Services, NACS,
NetWare Asynchronous Services Interface, NASI, NetWare Core Protocol,
NCP, NetWare Directory Services, NDS, NetWare DOS Requester, NDR,
NetWare Express, NetWare Loadable Module, NLM, NetWare LU6.2, NetWare
Management Agent, NetWare Management System, NetWare MHS, NetWare
MultiProtocol Router, NetWare NFS, NetWare Requester, NetWare RPC,
NetWare Runtime, NetWare SQL, NetWare Standard Message Format,
NetWave, Network Support Encyclopedia, NetWare System Interface, NSI,
NetWare 3270 LAN Workstation, NetWare 3270 LAN Workstation for DOS,
NetWare 3270 LAN Workstation for Windows, NE/2, NE/2-32, NE1000,
NE1500T, NE2000, NE2100, NE3200, NE32HUB, Novell DOS, Novell Labs,
Novell Virtual Terminal, NVT, NTR2000, Open Data-Link Interface, ODI,
Packet Burst, Rapid Filer, Red Box, Remote User Interface, RUI,
RX-Net/2, Serving FTP, SFT, Sequenced Packet Exchange, Store Front,
Street Smarts, Topology Specific Module, TSM, TSA, Transaction
Tracking System, TTS, Turbo RX-Net, Virtual Loadable Module, and VLM
are trademarks of Novell, Inc.</PARA>

<PARA>UNIX is a registered trademark of Novell, Inc. in
the United States and other countries, licensed exclusively through
X/Open Company, Ltd.</PARA>

<PARA>Direct Connect, Independent Manufacturers Support Program, and
NetWire are service marks of Novell, Inc.</PARA>

<PARA>Novell Authorized Reseller is a collective mark of Novell,
Inc.</PARA>

<PARA>3Com and 3+Share are registered trademarks of 3Com
Corporation.</PARA>

<PARA>AMD is a trademark of Advanced Micro Devices.</PARA>

<PARA>ARCnet is a registered trademark of Datapoint
Corporation.</PARA>

<PARA>AT&T is a registered trademark of AT&T.</PARA>

<PARA>Apple, Apple Logo, AppleShare, AppleTalk, EtherTalk,
ImageWriter, LaserWriter, LocalTalk, and Macintosh are
registered trademarks of Apple Computer, Inc.  AppleTalk protocols and
computer programs are licensed from Apple Computer, Inc.</PARA>

<PARA>AppleScript, Balloon Help, Finder, MacTCP, Power Macintosh
and System 7 are trademarks of Apple Computer, Inc.</PARA>

<PARA>Attachmate is a registered trademark of Attachmate
Corporation.</PARA>

<PARA>Blast, Blast Professional DOS, and Blast Professional Server are registered trademarks of Blast, Inc.</PARA>

<PARA>Bocamodem is a trademark of Boca Research, Inc.</PARA>

<PARA>CALPAK is a registered trademark of CALPAK Corporation.</PARA>

<PARA>Cheyenne is a registered trademark of Cheyenne Software, Inc.</PARA>

<PARA>Citrix is a registered trademark of Citrix Systems, Inc.</PARA>

<PARA>Citizen is a registered trademark of Tokei Kabushiki
Kaisha.</PARA>

<PARA>COMPAQ is a registered trademark of Compaq Computer
Corporation.</PARA>

<PARA>CompuServe is a registered trademark of CompuServe, Inc.</PARA>

<PARA>Datastorm is a registered trademark of Datastorm Technologies,
Inc.</PARA>

<PARA>DDS is a trademark of Sony Corporation.</PARA>

<PARA>DEC, VAX, VMS, VT100, VT200 and VT52 are trademarks of Digital
Equipment Corporation.</PARA>

<PARA>Digiboard C/X System, Digiboard Xem, and Digi International are
trademarks of Digi International.</PARA>

<PARA>Discovery is a trademark of Creative Technology, Ltd.</PARA>

<PARA>DynaText is a registered trademark of Electronic Book Technologies, Inc.</PARA>

<PARA>Epson is a registered trademark of Seiko Epson
Corporation.</PARA>

<PARA>FAXserve is a trademark of Cheyenne Communications, Inc.</PARA>

<PARA>GCH Systems is a trademark and EasyData is a registered
trademark of GCH Systems, Inc.</PARA>

<PARA>GE Information Services is a trademark of General Electric
Company, USA, which is not connected with the General Electric Company
p.l.c. of England.</PARA>

<PARA>GVC is a registered trademark of GVC Corporation.</PARA>

<PARA>Hayes is a registered trademark of Hayes Microcomputer Products,
Inc.</PARA>

<PARA>Hercules is a registered trademark of Hercules Computer
Technology.</PARA>

<PARA>Hewlett-Packard, Deskjet, HP, Laserjet, PCL, and Vectra
are registered trademarks of Hewlett-Packard Company.</PARA>

<PARA>IBM, AS/400, AT, Micro Channel, NetView, OS/2, OS/400,
ProPrinter, PS/2, and Systems Application Architecture are registered
trademarks of International Business Machines Corporation.</PARA>

<PARA>CICS/VS, ES/9000, IBM Operating System/2 Local Area Network
Server (LAN Server), MVS/TSO, Presentation Manager, SAA, VTAM, and XT
are trademarks of International Business Machines Corporation.</PARA>

<PARA>Intel is a registered trademark of Intel Corporation.</PARA>

<PARA>IntelliPort and Computone are registered trademarks of Computone
Corporation.</PARA>

<PARA>LAN Manager, LAN Manager Server, and MS Windows NT are
trademarks of Microsoft Corporation.</PARA>

<PARA>LapTALK Plus EthernetTALK TokenetTALK are trademarks and OSITECH
is a registered trademark of OSITECH Communications, Inc.</PARA>

<PARA>Lotus is a registered trademark and cc:Mail is a trademark of
Lotus Development Corporation.</PARA>

<PARA>Microsoft and MS-DOS are registered trademarks of Microsoft
Corporation.</PARA>

<PARA>Multi-Tech is a trademark of Multi-Tech Systems, Inc.</PARA>

<PARA>NET/MASTER is a registered trademark of Systems Center.</PARA>

<PARA>NFS is a registered trademark of Sun Microsystems, Inc.</PARA>

<PARA>Okidata, Okitel, and Microline are registered trademarks of Oki
Electric Industry Co., Ltd.</PARA>

<PARA>ONboard, ONboard/E, ONboard2, Brumby, and Stallion are
trademarks of Stallion Technologies, Inc.</PARA>

<PARA>Panasonic is a registered trademark of Panasonic Office
Automation.</PARA>

<PARA>PC Anywhere and Symantec are registered trademarks of Symantec
Corporation.</PARA>

<PARA>PC-Term is a registered trademark of Crystal Point, Inc.</PARA>

<PARA>Pinwriter, Spinwriter, and NEC are registered trademarks of NEC
Corporation.</PARA>

<PARA>PostScript is a registered trademark of Adobe Systems
Incorporated.</PARA>

<PARA>PowerBook is a trademark of Apple Computer, Inc.</PARA>

<PARA>Qmodem Pro and Mustang Software, Inc. are trademarks of Mustang
Software, Inc.</PARA>

<PARA>Racal is a registered trademark of Racal Electronics plc.</PARA>

<PARA>RUMBA, RUMBA/400, and Wall Data are registered trademarks of
Wall Data, Inc.</PARA>

<PARA>SDI is a registered trademark of Systems Data, Inc.</PARA>

<PARA>Sharp is a registered trademark of Sharp Electronics
Corporation.</PARA>

<PARA>Smartmodem 1200 is a trademark of Hayes Microcomputer Products,
Inc.</PARA>

<PARA>Smart Term and Smart Move are registered trademarks of Persoft,
Inc.</PARA>

<PARA>SMC is a registered trademark of Standard microsystems
Corporation.</PARA>

<PARA>Softerm PC and Softerm are registered trademarks of Softronics,
Inc.</PARA>

<PARA>SQL Server is a trademark of Sybase, Inc.</PARA>

<PARA>Stuffit! is a trademark of Aladdin Systems.</PARA>

<PARA>Supra Faxmodem is a trademark and Supra is a registered trademark
of Supra Corporation.</PARA>

<PARA>Telepathy and Entrasensory Software are registered trademarks of
Extrasensory Software</PARA>

<PARA>Twex, Twex Workstation for DOS, Twex Workstation for Windows,
and SITER Workstation for Windows are trademarks of Farabi
Technology.</PARA>

<PARA>UFO, Galaxy, Gemini, and GNX are registered trademarks of Galaxy
Networks, Inc.</PARA>

<PARA>Unicode is a registered trademark of Transoft Ltd.</PARA>

<PARA>Vadic is a registered trademark of Racal-Datacom, Inc.</PARA>

<PARA>WNIM is a registered trademark of Gateway Communications,
Inc.</PARA>

<PARA>WordPerfect is a registered trademark of WordPerfect
Corporation.</PARA>

<PARA>Xerox and Xerox Diablo are registered trademarks of Xerox
Corporation.</PARA>

<PARA>X/Open is a trademark of X/Open Company, Ltd.</PARA>

<PARA>ZyXEL is a trademark of ZyXEL.</PARA>

<PARA>All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.</PARA>

</LEGALNOTICE>

<LEGALNOTICE>
<TITLE>Copyright Notices</TITLE>

<PARA>⌐Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.</PARA>

<PARA>
<SIMPLELIST>
<MEMBER>Novell, Inc.</MEMBER>
<MEMBER>122 East 1700 South</MEMBER>
<MEMBER>Provo, UT 84606</MEMBER>
<MEMBER>U.S.A.</MEMBER>
</SIMPLELIST>
</PARA>

</LEGALNOTICE>
</BOOKINFO>
<PREFACE><TITLE><BEGINPAGE PAGENUM=10 ID="BP1"><XMARK id="FM44605">Conventions</TITLE><PARA>This guide uses the following conventions.</PARA>
<SECT1><TITLE>
Command and Message Formats</TITLE><PARA>Commands are shown as follows:</PARA>
<LITERALLAYOUT><USERINPUT>LOGIN <REPLACEABLE>SERVER_NAME</REPLACEABLE><USERINPUT>/</USERINPUT><REPLACEABLE>USER_NAME</REPLACEABLE> <KEYCAP><Enter></KEYCAP>
</USERINPUT></LITERALLAYOUT>
<PARA><USERINPUT>Bold</USERINPUT> text (<USERINPUT>LOGIN</USERINPUT> and <USERINPUT>/</USERINPUT>) indicates parts of the command that you must type exactly as shown.</PARA>
<PARA><REPLACEABLE>Italic</REPLACEABLE> text (<REPLACEABLE>SERVER_NAME</REPLACEABLE> and <REPLACEABLE>USER_NAME</REPLACEABLE>) indicates variable information that is specific to your installation. You must supply appropriate information in place of the variables.</PARA>
<PARA>The text between the <angle brackets> (<KEYCAP><Enter></KEYCAP>) identifies a key that you press.</PARA>
</SECT1>
<SECT1><TITLE>Long Command Lines</TITLE><PARA>Commands that are too long to fit on a single line are shown on multiple lines, as follows:</PARA>
<LITERALLAYOUT><USERINPUT>PRINT README.TXT INFO.TXT INSTALL.PS DATALIST.DAT FILELIST.TXT RESUME.DOC RECIPE.CHP <KEYCAP><Enter></KEYCAP>
</USERINPUT></LITERALLAYOUT>
<PARA>Each line after the first is indented. When you type the command, DO NOT type the command on multiple lines.</PARA>
</SECT1><BEGINPAGE PAGENUM=11 ID="BP2">
<SECT1><TITLE>
Menu Choices</TITLE><PARA>When you must make a series of choices from menus in order to display a particular screen, the choices are shown as follows:</PARA>
<PARA><INTERFACE class=menuitem>Choice 1</INTERFACE><INTERFACE class=menuitem>Choice 2</INTERFACE><INTERFACE class=menuitem>Choice 3</INTERFACE><INTERFACE class=menuitem>Choice 4</INTERFACE><INTERFACE class=menuitem>Choice 5</INTERFACE></PARA>
<PARA>There are two ways to select a choice from a menu:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Use the arrow keys to highlight the choice. </PARA>
</LISTITEM>
<LISTITEM><PARA>Type the first letter of the choice. (If more than one choice starts with the same letter, type successive letters until the correct choice is highlighted.)</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Once the correct choice is highlighted, press <<KEYCAP>Enter</KEYCAP>>.</PARA>
</SECT1>
<SECT1><TITLE>Using the Different Screen Types</TITLE><PARA>
When you select an option from the main menu, additional menus or displays appear. The displays can be lists, forms, or confirmation boxes.</PARA>
<SECT2><TITLE>Using Lists</TITLE><PARA>Select items from a list the same way you select a menu choice. You can also add items to and delete items from some lists. </PARA>
<PARA>Lists may have more than one column, and they may extend below the bottom edge of your monitor. </PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>To scroll through list items, use the <KEYCAP>arrow</KEYCAP> keys. </PARA>
</LISTITEM>
<LISTITEM><PARA>To jump to the bottom of the list, press <KEYCAP><PageDown></KEYCAP>. </PARA>
</LISTITEM>
<LISTITEM><PARA>To jump to the top of the list, press <KEYCAP><PageUp></KEYCAP>. </PARA>
</LISTITEM><BEGINPAGE PAGENUM=12 ID="BP3">
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Using Forms</TITLE><PARA>
Forms are screens that contain fields. Some fields allow you to type in information. Other fields display menus of values from which you select.</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>To move between fields, use the arrow keys or <KEYCAP><Enter</KEYCAP>>. When you press <KEYCAP><Enter></KEYCAP>, the cursor moves to the next field in the form. </PARA>
</LISTITEM>
<LISTITEM><PARA>To edit the information in the field, highlight the field and press <KEYCAP><Enter></KEYCAP>. </PARA>
</LISTITEM>
<LISTITEM><PARA>To replace the information in a field, use <KEYCAP><Delete></KEYCAP> to clear the field. </PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Using Confirmation Boxes</TITLE><PARA>
Confirmation boxes display when you exit a module or create or delete items. Confirm or cancel your action by selecting Yes or No and pressing <KEYCAP><Enter></KEYCAP>.</PARA>
<PARA></PARA>
</SECT2>
</SECT1>
<SECT1><TITLE>Using Key Combinations</TITLE><PARA>When you must press two keys simultaneously, the instruction looks like this example:</PARA>
<PARA><KEYCAP><Shift-F7></KEYCAP></PARA>
<PARA>When you must press two keys simultaneously and then release them before pressing an additional key, the instruction looks like this example:</PARA>
<PARA><KEYCAP><Shift-F7> <a></KEYCAP></PARA>
</SECT1><BEGINPAGE PAGENUM=13 ID="BP4">
<SECT1><TITLE>Using Special Keys</TITLE><PARA>When you are using the administration utility, the following keys perform as described:</PARA>
<INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="9*">
<COLSPEC colname=2 colwidth="17*">
<TBODY><ROW><ENTRY colname=1><PARA><KEYCAP><Backspace></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><Backspace></KEYCAP> returns the highlight to the top menu item.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><Delete></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><Delete></KEYCAP> removes selected information from a list.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><Down-arrow></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><Down-arrow></KEYCAP> moves the highlight to the next item down in a menu or form.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><Enter></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA>When you are using a form, <KEYCAP><Enter></KEYCAP> copies information from the form into the database and moves the highlight to the next item on the form.</PARA><PARA>When you are using a list,<KEYCAP> <Enter></KEYCAP> moves selected information from the list to the field that called the list.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><Esc></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA>When a menu other than the main menu is displayed, <KEYCAP><Esc></KEYCAP> redisplays the previous menu.</PARA><PARA>When the main menu is displayed, <KEYCAP><Esc></KEYCAP> displays a confirmation box. Highlight Yes and press <KEYCAP><Enter></KEYCAP> to exit the program.</PARA><PARA>When you are performing a process, <KEYCAP><Esc></KEYCAP> terminates the process.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><Insert></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><Insert></KEYCAP> allows you to add new information by displaying a blank form in which to enter the information.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><PageDown></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><PageDown></KEYCAP> moves the highlight to the last item on a list.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><PageUp></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><PageUp></KEYCAP> moves the highlight to the first item on a list.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><KEYCAP><Up-arrow></KEYCAP></PARA></ENTRY>
<ENTRY colname=2><PARA><KEYCAP><Up-arrow></KEYCAP> moves the highlight to the previous item.</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<BEGINPAGE PAGENUM=14 ID="BP5"><PARA></PARA>
</SECT1>
</PREFACE>
<CHAPTER LABEL="1"><TITLE><BEGINPAGE PAGENUM=1 ID="BP6"><XMARK id="FMIntro">Introducing NetWare/IP</TITLE><PARA>NetWare/IP is a set of server and client software modules that extend NetWare« connectivity onto TCP/IP networks. NetWare/IP replaces the Internetwork Packet eXchange<SUPERSCRIPT>TM</SUPERSCRIPT> (IPX<SUPERSCRIPT>TM</SUPERSCRIPT>) protocol that provides the transport in the native NetWare environment with the industry-standard Internet Protocol (IP). Above and below the transport layers, NetWare/IP uses the same network hardware and software. Thus, you can use the same LAN drivers and datalink-level drivers as with native NetWare nodes. In addition, applications that run over IPX will continue to run identically over IP.</PARA>
<PARA>NetWare/IP both allows IP and IPX to coexist in the same NetWare network, and allows seamless interconnection of IPX and IP network segments. Clients throughout your internetwork can then access services on any NetWare or NetWare/IP server regardless of transport.</PARA>
<SECT1><TITLE>NetWare/IP Client Services</TITLE><PARA>NetWare/IP provides the following client services:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Access to services on NetWare/IP and NetWare servers</PARA>
</LISTITEM>
<LISTITEM><PARA>Access to servers in remote NetWare/IP domains</PARA>
</LISTITEM><BEGINPAGE PAGENUM=2 ID="BP7">
</ITEMIZEDLIST>
</SECT1>
<SECT1><TITLE>Using This Guide</TITLE><PARA>This manual provides the information you need to install, configure, and run the NetWare/IP client software. </PARA>
<INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="13*">
<COLSPEC colname=2 colwidth="13*">
<THEAD><ROW><ENTRY colname=1><PARA>If you want to . . .</PARA></ENTRY>
<ENTRY colname=2><PARA>Go to . . .</PARA></ENTRY>
</ROW>
</THEAD>
<TBODY><ROW><ENTRY colname=1><PARA>Gain an in-depth understanding of NetWare/IP background and concepts</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FM79912">Chapter 2 "Understanding NetWare/ IP"</IXREF>Chapter 2 "Understanding NetWare/ IP"</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Install the NetWare/IP software on a DOS or MS* Windows workstation.</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FMInsta">Chapter 3 "Installing and Configuring the NetWare/IP Client Software"</IXREF>Chapter 3 "Installing and Configuring the NetWare/IP Client Software" and <IXREF idref="FM70650">Appendix A "Planning Worksheets"</IXREF>Appendix A "Planning Worksheets"</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Understand the mechanics of installation keystroke entry, menus, and forms</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FM44605">"Conventions"</IXREF>"Conventions""</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Configure your NetWare/IP client</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FMInsta">Chapter 3 "Installing and Configuring the NetWare/IP Client Software"</IXREF>Chapter 3 "Installing and Configuring the NetWare/IP Client Software"</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Log in to the network from DOS or MS Windows</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FMRunni">Chapter 4 "Running the NetWare/IP Client Software"</IXREF>Chapter 4 "Running the NetWare/IP Client Software"</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Solve problems if they arise while installing, configuring, and running the NetWare/IP software</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FMRunni">Chapter 4 "Running the NetWare/IP Client Software"</IXREF>Chapter 4 "Running the NetWare/IP Client Software" and <IXREF idref="FM89185">Appendix B "Error Messages"</IXREF>Appendix B "Error Messages"</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Access services on a remote NetWare/IP domain</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FMRunni">Chapter 4 "Running the NetWare/IP Client Software"</IXREF>Chapter 4 "Running the NetWare/IP Client Software"</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Remove the NetWare/IP software from a client workstation</PARA></ENTRY>
<ENTRY colname=2><PARA><IXREF idref="FMRemov">Chapter 5 "Removing the NetWare/IP Client Software"</IXREF>Chapter 5 "Removing the NetWare/IP Client Software"</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="2"><TITLE><BEGINPAGE PAGENUM=1 ID="BP8"><XMARK id="FM79912">Understanding NetWare/IP</TITLE><PARA>The NetWare/IP software allows NetWare« and its applications to run over the Internet Protocol (IP) in addition to the IPX<SUPERSCRIPT>TM</SUPERSCRIPT> protocol that traditionally has provided NetWare transport. The NetWare/IP client software allows you to</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Access NetWare/IP servers on TCP/IP networks</PARA>
</LISTITEM>
<LISTITEM><PARA>Access NetWare servers on IPX networks</PARA>
</LISTITEM>
<LISTITEM><PARA>Access servers in remote NetWare/IP domains</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>This chapter provides background information to help you understand NetWare/IP including an overview of the components that make up a NetWare/IP network and an in depth discussion of the software that makes up the client component.</PARA>
<SECT1><TITLE>NetWare/IP Network Components</TITLE><PARA>
There are several basic NetWare/IP components that are required on a NetWare/IP network. This section lists and briefly describes each component and explains how the components work together to provide NetWare services on your TCP/IP network. The remainder of the chapter provides additional detail about the client component. For information on any of the other components, refer to the <CITETITLE><BXREF book="adminenu"Collection="nwip20">
NetWare/IP Administrator's Guide</BXREF></CITETITLE>.</PARA>
<SECT2><TITLE>
NetWare/IP Support Services</TITLE><BEGINPAGE PAGENUM=2 ID="BP9"><PARA>The NetWare/IP support services provide the framework for the NetWare/IP network by supplying information about the location and availability of services and routes within the network. In an IPX network, NetWare servers broadcast this information every 60 seconds. IP networks, however, do not support this type of internetwork broadcast. Therefore, NetWare/IP provides the following support services to emulate the IPX broadcast mechanism:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>The
Domain SAP/RIP Server (
DSS) maintains two types information required by NetWare servers and clients:</PARA>
</LISTITEM>
<LISTITEM><PARA>
Service Advertising Protocol (
SAP) information about the available NetWare services.</PARA>
</LISTITEM>
<LISTITEM><PARA>
Routing Information Protocol (
RIP) information about routes between NetWare servers.</PARA>
<PARA>Once configured, the DSS automatically maintains this information and makes it available to all NetWare/IP nodes. NetWare/IP servers and clients use DSS to obtain service and routing information and global NetWare/IP parameters.</PARA>
</LISTITEM>
<LISTITEM><PARA>The
Domain Name System (
DNS) is a distributed database system used to locate computers in TCP/IP internetworks. NetWare/IP servers and clients use DNS to locate the nearest DSS.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>
NetWare/IP Server</TITLE><PARA>The NetWare/IP server is a NetWare 4 server that is configured with TCP/IP and NetWare/IP NetWare Loadable Modules (NLMs). The NetWare/IP server provides NetWare services to clients on a TCP/IP network.</PARA>
</SECT2>
<SECT2><TITLE>
NetWare/IP Client</TITLE><PARA>The NetWare/IP client is a workstation that is configured with the NetWare/IP client software. The NetWare/IP software enables the client to access NetWare services over a TCP/IP network. For more information on the NetWare/IP client software, <IXREF idref="FM36208">see "NetWare/IP Client for DOS and MS* Windows" on page 2-5</IXREF>.</PARA>
</SECT2><BEGINPAGE PAGENUM=3 ID="BP10">
<SECT2><TITLE>How the
Components Work Together</TITLE><PARA>The NetWare/IP components work together as follows to provide NetWare services on the TCP/IP network:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>When a server starts up, it queries DNS for the nearest DSS. </PARA>
</LISTITEM>
<LISTITEM><PARA>The server then queries DSS for the global configuration information. The server also registers its services with the DSS and queries the DSS about other services that are available within the NetWare/IP network. While the server is running, it continues to exchange service information with the DSS at a preconfigured interval.</PARA>
</LISTITEM>
<LISTITEM><PARA>When a client system starts up, it must also locate DSS to obtain the global configuration information and the service and routing information for the network. If the client does not know the location of DSS, it first queries DNS.</PARA>
</LISTITEM>
<LISTITEM><PARA>The client then locates the nearest NetWare/IP server, either using its local configuration information or by querying DSS. The client then directs its NetWare/IP queries to that server.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA><IXREF idref="FM37314">Figure 2-1</IXREF> further illustrates how the NetWare/IP components work together.</PARA>
<BEGINPAGE PAGENUM=4 ID="BP11"><FIGURE LABEL="2-1"><TITLE><XMARK id="FM37314">Relationship Between Components</TITLE><GRAPHIC FILEREF="cmpnts2.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=5 ID="BP12">
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM36208">NetWare/IP Client for DOS and MS* Windows</TITLE><PARA>The NetWare/IP client software extends NetWare capabilities to DOS and MS Windows workstations on TCP/IP networks. With NetWare/IP, NetWare services and applications run identically to how they run in native IPX-based NetWare environments.</PARA>
<SECT2><TITLE>Client Software</TITLE><PARA>To provide seamless connectivity in a TCP/IP environment, the NetWare/IP client uses the same Link Support Layer<SUPERSCRIPT>TM</SUPERSCRIPT> (LSL<SUPERSCRIPT>TM</SUPERSCRIPT>) driver, Open Data-Link Interface<SUPERSCRIPT>TM</SUPERSCRIPT> (ODI<SUPERSCRIPT>TM</SUPERSCRIPT>) driver, and NetWare DOS Requester as a native NetWare client. However, to provide the TCP/IP transport, NetWare/IP replaces the IPX driver with the following software modules:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>TCPIP.EXE, which provides the TCP/IP protocol stack</PARA>
</LISTITEM>
<LISTITEM><PARA>NWIP.EXE, which provides the NetWare/IP driver</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA><IXREF idref="FM51397">Figure 2-2</IXREF> compares the NetWare/IP client modules with the traditional IPX-based client modules. A description of each NetWare/IP client software module follows the figure.</PARA>
<BEGINPAGE PAGENUM=6 ID="BP13"><FIGURE LABEL="2-2"><TITLE><XMARK id="FM51397">NetWare/IP Client NetWare Client Comparison</TITLE><GRAPHIC FILEREF="client.tif"></GRAPHIC>
</FIGURE>
<SECT3><TITLE>ODI Driver</TITLE><PARA>An ODI driver is a LAN driver that adheres to the Open Data-Link Interface (ODI) specification. The LAN driver serves as a link between the physical network and the operating system. An ODI driver connects directly to the network board and the LSL driver.</PARA>
</SECT3>
<SECT3><TITLE>LSL Driver</TITLE><PARA>The Link Support Layer (LSL) driver acts as an intermediary between the ODI driver and the protocol stack. In the NetWare/IP environment, the LSL passes packets of network data between the ODI driver and the TCP/IP protocol stack.</PARA>
</SECT3><BEGINPAGE PAGENUM=7 ID="BP14">
<SECT3><TITLE>TCP/IP Protocol Stack</TITLE><PARA>The TCP/IP protocol stack provides the software NetWare/IP uses to transport data through the network. TCP/IP is an industry-standard suite of networking protocols.</PARA>
</SECT3>
<SECT3><TITLE>NetWare/IP Driver</TITLE><PARA>The NetWare/IP driver provides the interface between the TCP/IP protocol stack and the NetWare DOS Requester. Thus, the NetWare/IP driver is the software component that enables NetWare applications and services to run over TCP/IP.</PARA>
</SECT3>
<SECT3><TITLE>NetWare DOS Requester</TITLE><PARA>The NetWare DOS Requester is the link between workstation applications, DOS, and the network. It performs tasks such as file and print redirection, connection maintenance, and packet handling.</PARA>
<PARA>The NetWare DOS Requester is composed of a number of modules called Virtual Loadable Modules (VLMs) that can be loaded as needed to perform specific functions. For example, the NWP.VLM establishes and maintains connections, logins, and logouts; the FIO.VLM handles file input/output; the REDIR.VLM performs DOS redirection services.</PARA>
<PARA>The VLM Manager (VLM.EXE) manages communication between the individual VLMs and applications and controls memory services, allocation, and management. </PARA>
</SECT3>
<SECT3><TITLE>DNS Resolver</TITLE><PARA>In addition to running the modules listed in <IXREF idref="FM51397">Figure 2-2</IXREF>, the NetWare/IP client also requires
DNS client, or resolver, software. The DNS client software enables the client to query DNS for host information. In NetWare/IP, clients query DNS to locate the nearest DSS.</PARA>
</SECT3><BEGINPAGE PAGENUM=8 ID="BP15">
</SECT2>
<SECT2><TITLE><XMARK id="FM28546">Client Configuration</TITLE><PARA>The NetWare/IP client requires both local and network-wide configuration parameters in order to run. These parameters are detailed in the following sections.</PARA>
<SECT3><TITLE>Local Parameters</TITLE><PARA>The NetWare/IP client obtains its local configuration either from files stored in its local NET.CFG and RESOLV.CFG files or from a BOOT Protocol (BOOTP) server. </PARA>
<PARA>A BOOTP server contains a centralized database of client configuration information. If the NetWare/IP client cannot find its local configuration in its NET.CFG file, it queries the BOOTP server. The location of the client configuration information is determined at installation. If a BOOTP server is not used, you must manually configure the client at installation.</PARA>
<PARA>There are two types of BOOTP servers used to configure NetWare/IP clients:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>BOOTP server, which provides TCP/IP configuration information</PARA>
</LISTITEM>
<LISTITEM><PARA>Extended BOOTP server, which provides NetWare/IP configuration information</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>You can use either or both types of BOOTP servers to simplify the client configuration process.</PARA>
<SECT4><TITLE>Required Parameters</TITLE><PARA>The NetWare/IP client requires the following local parameters at startup. All of the required parameters must be configured during installation as follows:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>IP address, which specifies the IP address of the client system</PARA>
</LISTITEM>
<LISTITEM><PARA>Subnetwork mask, which specifies the subnetwork mask for the TCP/IP network</PARA>
</LISTITEM>
<LISTITEM><PARA>Default router, which specifies the IP address of the default router, if any, for this subnetwork</PARA>
</LISTITEM><BEGINPAGE PAGENUM=9 ID="BP16">
<LISTITEM><PARA>DNS domain, which specifies the default DNS domain name</PARA>
</LISTITEM>
<LISTITEM><PARA>Default DNS name servers, which specifies the IP addresses of up to three DNS name servers for the DNS domain</PARA>
</LISTITEM>
<LISTITEM><PARA>NetWare/IP domain, which specifies the NetWare/IP domain to which this client belongs</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT4>
<SECT4><TITLE>Optional Parameters</TITLE><PARA>The NetWare/IP client may optionally use the following parameters to optimize performance:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Initial DSS contact retries, which specifies the number of times the client will attempt to communicate with a given DSS at startup. The default is two retries. This parameter can only be modified by manually editing the net.cfg file.</PARA>
</LISTITEM>
<LISTITEM><PARA>Retry interval, which specifies the time interval in seconds between attempts to retry communicating with a given DSS at startup. The default is ten seconds. This parameter can only be modified by manually editing the net.cfg file.</PARA>
</LISTITEM>
<LISTITEM><PARA>Preferred DSSes, which specifies the hostnames, IP addresses, or subnetwork IP addresses of up to five DSSes that are closest to this client. This parameter can be configured during installation.</PARA>
</LISTITEM>
<LISTITEM><PARA>Nearest server, which specifies the IP address or subnetwork IP address of the NetWare/IP server closest to this client. This parameter can be configured during installation.</PARA>
</LISTITEM>
<LISTITEM><PARA>NSQ Broadcast, which specifies whether this client will use Nearest Server Query (NSQ) broadcasts to locate the nearest server. By default, NSQ broadcast is set to on. This parameter can only be modified by manually editing the net.cfg file.</PARA>
</LISTITEM>
<LISTITEM><PARA>NetWare/IP 1.1 compatibility, which specifies whether this client can access NetWare/IP 1.1 servers. By default, NetWare/IP 1.1 compatibility is set to off. This parameter can only be modified by manually editing the net.cfg file.</PARA>
</LISTITEM><BEGINPAGE PAGENUM=10 ID="BP17">
</ITEMIZEDLIST>
</SECT4>
</SECT3>
<SECT3><TITLE>Global Parameters</TITLE><PARA>In addition to the local parameters, the NetWare/IP client also obtains network-wide configuration information from the DSS, such as the virtual IPX network number, UDP port numbers for NetWare/IP service, and DSS-NetWare/IP synchronization interval. </PARA>
<PARA>In order to start up for the first time, the NetWare/IP client must obtain the global configuration parameters from the DSS. The client then saves the parameters to a local file. The next time the client starts up, it will again look for the DSS to obtain the current configuration. However, if it cannot find the DSS, it defaults to the configuration it used the last time it was up.</PARA>
</SECT3>
<SECT3><TITLE>Configuration Files</TITLE><PARA>The client configuration information for NetWare/IP is stored on the following two configuration files:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>NET.CFG, which contains TCP/IP and NetWare/IP configuration information</PARA>
</LISTITEM>
<LISTITEM><PARA>RESOLV.CFG, which contains DNS client (resolver) configuration information</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>You can edit the information stored in these files using any text editor.</PARA>
</SECT3>
</SECT2>
<SECT2><TITLE>Client Startup Process</TITLE><PARA>The NetWare/IP client requires that TCP/IP be loaded and ready before NetWare/IP can run. When TCP/IP is ready, the NetWare/IP client starts up as follows:</PARA>
<ORDEREDLIST NUMERATION=ARABIC><LISTITEM><PARA>The client obtains its local configuration parameters from one of the following locations:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Local NET.CFG and RESOLV.CFG files</PARA>
</LISTITEM>
<LISTITEM><PARA>BOOTP server</PARA>
</LISTITEM>
<LISTITEM><PARA>Extended BOOTP server</PARA>
</LISTITEM>
<LISTITEM><PARA>The client obtains network-wide parameters from DSS. The client locates DSS using one of the following:</PARA>
</LISTITEM><BEGINPAGE PAGENUM=11 ID="BP18">
<LISTITEM><PARA>Preferred DSS specified in its local configuration, if any</PARA>
</LISTITEM>
<LISTITEM><PARA>DNS query</PARA>
</LISTITEM>
<LISTITEM><PARA>The client locates the closest NetWare/IP server using one of the following:</PARA>
</LISTITEM>
<LISTITEM><PARA>Nearest server specified in its local configuration, if any</PARA>
</LISTITEM>
<LISTITEM><PARA>UDP broadcast</PARA>
</LISTITEM>
<LISTITEM><PARA>DSS query</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</LISTITEM>
</ORDEREDLIST>
</SECT2>
<SECT2><TITLE>Limitations on Client Access</TITLE><PARA>Currently NetWare/IP imposes the following limitations on client access to NetWare services:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>NetWare/IP clients can access NetWare printers only if you set up a forwarding gateway between the IPX segment on which the printer is located and the IP backbone.</PARA>
</LISTITEM>
<LISTITEM><PARA>NetWare/IP supports IPX
NetBIOS only on local subnetworks: IPX NetBIOS broadcasts do not carry across IP routers. If you need NetBIOS capability over TCP/IP, you can substitute the
RFCNBIOS program provided with the NetWare/IP software.</PARA>
</LISTITEM>
<LISTITEM><PARA>Products that enhance IPX routing, such as dynamic links, cannot be used with NetWare/IP.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Take these limitations into account when planning your network by locating clients requiring these services on IPX segments.</PARA>
</SECT2>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="3"><TITLE><BEGINPAGE PAGENUM=1 ID="BP19"><XMARK id="FMInsta">Installing and Configuring the NetWare/IP Client Software</TITLE><PARA>Once a NetWare/IP<SUPERSCRIPT>TM</SUPERSCRIPT> server and its support services are running on the TCP/IP network, you can install and configure the NetWare/IP client software on your workstation to enable you to access NetWare« services and applications.</PARA>
<PARA>This chapter presents information specific to installation of the NetWare/IP client software. For more information about using and customizing NetWare client software, refer to the<CITETITLE> Workstation Basics and Installation </CITETITLE>manual, which is part of the NetWare 4 documentation set.</PARA>
<SECT1><TITLE>Setting Up Server-Based Installation</TITLE><PARA>If you have access to a NetWare server, you can install the NetWare/IP client software from a server directory instead of from diskettes. Your system administrator can use the following procedure to set up a login and server directory for this purpose. </PARA>
<PARA>The procedure includes examples of NetWare administration commands that may need to be adapted for your site and NetWare version. Refer to the documentation for your version of NetWare for more information about the NetWare administration procedures mentioned in this procedure.</PARA>
<PROCEDURE><STEP><PARA>Log in as SUPERVISOR on the NetWare server where you want to locate the installation directory.</PARA>
<PARA>The directory requires approximately 5 MB of disk space.
</PARA>
</STEP>
<STEP><PARA>Create a directory for the NetWare/IP client software.
</PARA>
<PARA>For example:
<LITERALLAYOUT><USERINPUT>MKDIR F:\USER\NWCLIENT
</USERINPUT><BEGINPAGE PAGENUM=2 ID="BP20"></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Copy the contents of all of the client diskettes to this directory.
</PARA>
<PARA>Use XCOPY or NCOPY to ensure that contents of subdirectories are duplicated on the server. Do not set up separate directories for each diskette. For example:
<LITERALLAYOUT><USERINPUT>NCOPY A: F:\USER\NWCLIENT /S
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Use the SYSCON or NETADMIN utility to add an installation login (for example, NWCLIENT).
</PARA>
</STEP>
<STEP><PARA>Modify the login script for the new login to map a drive to the directory you created for the client software and place the user in that directory after logging in.
</PARA>
<PARA>For example, if the directory is on VOL1:, you could include the following lines in the login script:
<LITERALLAYOUT><USERINPUT>   MAP G:=VOL1:\USER\NWCLIENT  G:
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Set up a password for the new login and set any additional restrictions you want for security purposes.
</PARA>
</STEP>
<STEP><PARA>Give the installation login Read and Filescan rights to the files in the client software directory.
</PARA>
<PARA>Be sure to provide access to all files and subdirectories. For example:
<LITERALLAYOUT><USERINPUT>GRANT R F FOR F:\USER\NWCLIENT TO NWCLIENT /S/F
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Log out and log back in using the newly created login to verify that the login and directory are correctly set up.
</PARA>
<PARA>Logging in should set the current directory to the client software directory you created, and the DIR command should list the files and subdirectories.
</PARA>
</STEP>
</PROCEDURE>
<PARA>After the server login and directory are set up, the system administrator can inform users of the server name and login when distributing the filled-in Client Worksheets.</PARA>
</SECT1><BEGINPAGE PAGENUM=3 ID="BP21">
<SECT1><TITLE>Setting Up the NetWare/IP Client</TITLE><PARA>This section provides information to help you successfully set up your NetWare/IP client workstation and includes the following sections:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Client system prerequisites</PARA>
</LISTITEM>
<LISTITEM><PARA>Using the NetWare/IP Client Installation program</PARA>
</LISTITEM>
<LISTITEM><PARA>Installing the NetWare/IP Client Software</PARA>
</LISTITEM>
<LISTITEM><PARA>Modifying the NetWare/IP Configuration</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<SECT2><TITLE>Client System Prerequisites</TITLE><PARA>This section explains conditions your workstation must meet before you can install and run the NetWare/IP client software and provides information you need before running the installation program.</PARA>
<PARA>Each client workstation must meet the following requirements before you can configure and run NetWare/IP.</PARA>
<SECT3><TITLE>Hardware Requirements</TITLE><ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Computer</PARA>
<PARA>To run the DOS client software, you need an IBM PC/XT*, PC/AT*, PS/2*, or an 80286*-, 80386*-, or 80486*-based compatible. </PARA>
<PARA>To run the MS Windows client software, you need an IBM PC/AT or PS/2, or an 80286-, 80386-, or 80486-based compatible. </PARA>
</LISTITEM>
<LISTITEM><PARA>Network Board</PARA>
<PARA>All workstations must have a network board that is supported by NetWare or has a NetWare-compatible ODI<SUPERSCRIPT>TM</SUPERSCRIPT> driver included. The Novell SLIP/PPP driver is also supported.</PARA>
</LISTITEM>
<LISTITEM><PARA>Memory</PARA>
<PARA>The NetWare/IP DOS client software uses approximately 120 KB of memory. The recommended minimum memory for DOS systems is 640 KB. The recommended minimum memory for MS Windows systems is 4 MB.</PARA>
</LISTITEM><BEGINPAGE PAGENUM=4 ID="BP22">
<LISTITEM><PARA>Disk Space</PARA>
<PARA>The following space is needed to store the client files:</PARA>
</LISTITEM>
<LISTITEM><PARA>1 MB in the NetWare/IP client directory (C:\NWCLIENT by default).</PARA>
</LISTITEM>
<LISTITEM><PARA>1 MB in the TCP/IP directory (C:\NET by default).</PARA>
</LISTITEM>
<LISTITEM><PARA>2.5 MB in the MS Windows directory.</PARA>
</LISTITEM>
<LISTITEM><PARA>0.5 MB for temporary files created while the software is running.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT3>
<SECT3><TITLE>Software Requirements</TITLE><ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Operating System</PARA>
<PARA>IBM PC-DOS v3.3 (or later), Microsoft MS-DOS v3.3 (or later), or NOVELL DOS« v6.0 (or later) must be installed on the workstation. </PARA>
<NOTE><PARA>If you plan to run MS Windows 3.1 with NOVELL DOS, make sure the date of your COMMAND.COM file is 4/92 or later. Contact your NetWare/IP vendor if you need a newer COMMAND.COM.</PARA>
</NOTE>
</LISTITEM>
<LISTITEM><PARA>MS Windows (optional)</PARA>
<PARA>If you plan to install MS Windows client support, the workstation must have MS Windows 3.0 (or later) installed. You can use a private (standalone) MS Windows, or use a shared (server) version of MS Windows. <IXREF idref="FM39971">See "Restoring Your MS Windows Files" on page 5-8</IXREF> for the files to install in the server MS Windows directory. </PARA>
<PARA>MS Windows must be completely installed and able to run correctly before you install the NetWare/IP client software so that the installation program can modify specific MS Windows configuration files and install other files into MS Windows subdirectories.</PARA>
</LISTITEM>
<LISTITEM><PARA>CONFIG.SYS file settings</PARA>
<PARA>Your CONFIG.SYS file (in the root directory of your boot disk) must have FILES and BUFFERS statements with the following (or greater) values:  FILES = 40 BUFFERS = 20</PARA>
<BEGINPAGE PAGENUM=5 ID="BP23"><PARA>You can change these values if desired after installation is complete.</PARA>
</LISTITEM>
<LISTITEM><PARA>APPEND commands</PARA>
<PARA>If you are using the APPEND command to allow programs to open data files in additional directories, you must disable this command before running the client installation program.</PARA>
<PARA>The following command cancels any APPEND command you have in effect:</PARA>
<LITERALLAYOUT><USERINPUT><USERINPUT>APPEND ;</USERINPUT>
</USERINPUT></LITERALLAYOUT>
</LISTITEM>
<LISTITEM><PARA>SHARE commands</PARA>
<PARA>You must disable the SHARE command if it is in effect before running the client installation program. To disable this command, temporarily comment the line in your CONFIG.SYS or AUTOEXEC.BAT file that runs SHARE, then restart the workstation.</PARA>
<WARNING><PARA>If you plan to run LAN WorkPlace« or LAN WorkGroup<SUPERSCRIPT>TM</SUPERSCRIPT> v4.1 or earlier, be sure to install this software on the workstation <EMPHASIS>before</EMPHASIS> you install NetWare/IP. The NetWare/IP client software has some files in common with LAN WorkPlace and LAN WorkGroup. The NetWare/IP files are fully compatible but include additional functionality.</PARA>
</WARNING>
</LISTITEM>
</ITEMIZEDLIST>
</SECT3>
</SECT2>
<SECT2><TITLE>Using the NetWare/IP Client Installation Program</TITLE><PARA>When you run the client installation program, the program displays the Client Installation forms, which are illustrated in <IXREF idref="FMClien">Figure 3-1</IXREF>. These forms prompt you for NetWare, TCP/IP, and NetWare/IP configuration information. For a description of each configuration parameter, <IXREF idref="FM28546">see "Client Configuration" on page 2-8</IXREF>. </PARA>
<PARA>The information required to complete the Client Installation forms can be found on your completed NetWare/IP Client Worksheet. A blank NetWare/IP Client Worksheet can be found in Appendix A. Make sure to have your NetWare/IP administrator complete this worksheet before you begin the installation procedure.</PARA>
<BEGINPAGE PAGENUM=6 ID="BP24"><FIGURE LABEL="3-1"><TITLE><XMARK id="FMClien">Client Installation Program Forms</TITLE><GRAPHIC FILEREF="install1.tif"></GRAPHIC>
<GRAPHIC FILEREF="install2.tif"></GRAPHIC>
</FIGURE>
<PARA>After you complete both forms, installation program uses the configuration information you supply to modify or create the following system files:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>DOS configuration files AUTOEXEC.BAT and CONFIG.SYS</PARA>
</LISTITEM>
<LISTITEM><PARA>NetWare configuration files NET.CFG, RESOLV.CFG, and STARTNET.BAT</PARA>
</LISTITEM>
<LISTITEM><PARA>MS Windows configuration files PROGMAN.INI, SYSTEM.INI, and WIN.INI</PARA>
</LISTITEM><BEGINPAGE PAGENUM=7 ID="BP25">
</ITEMIZEDLIST>
<PARA>These modifications are described in Chapter 5, "Removing the NetWare/IP Client Software." The program creates backup copies of your existing configuration files before making the changes.</PARA>
<PARA>The installation program also copies the following kinds of files to your workstation:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>NetWare tools for DOS and MS Windows</PARA>
</LISTITEM>
<LISTITEM><PARA>TCP/IP programs and utilities</PARA>
</LISTITEM>
<LISTITEM><PARA>VLM<SUPERSCRIPT>TM</SUPERSCRIPT> (Virtual Loadable Module<SUPERSCRIPT>TM</SUPERSCRIPT>) programs and utilities</PARA>
</LISTITEM>
<LISTITEM><PARA>Network board drivers</PARA>
</LISTITEM>
<LISTITEM><PARA>Unicode* tables with corresponding code page numbers and country codes</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Installing the NetWare/IP Client Software</TITLE><PARA>Before you install the NetWare/IP software on your workstation, be sure to get a completed NetWare/IP Client Worksheet from your system administrator. This worksheet provides all information required to install NetWare/IP. Use the following procedure to install the NetWare/IP client software:</PARA>
<PROCEDURE><STEP><PARA>Specify the installation drive and directory. </PARA>
<SUBSTEPS><STEP><PARA>If you are installing NetWare/IP from diskette, insert the WSDOS_1 disk in drive A or drive B and then type the drive letter and press
<KEYCAP><Enter></KEYCAP> to change to that drive.
</PARA>
</STEP>
<STEP><PARA>If you are installing NetWare/IP from a server, log in to your NetWare server using the login your system administrator created for the NetWare/IP installation.
</PARA>
<PARA>Consult your system administrator for the server name, login, and password.</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Type INSTALL and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>The workstation starts the installation program, which displays the first of two NetWare/IP Client Installation forms as shown in . This form includes a series of questions that you must answer before the installation program can continue with the installation.
</PARA><BEGINPAGE PAGENUM=8 ID="BP26">
</STEP>
<STEP><PARA>Specify the target directory.
</PARA>
<SUBSTEPS><STEP><PARA>To accept the default directory, C:\NWCLIENT, press the down arrow key.
</PARA>
</STEP>
<STEP><PARA>To specify a different target directory, type the new path and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Specify whether you want the installation program to modify the DOS configuration files automatically.
</PARA>
<SUBSTEPS><STEP><PARA>If you want to allow the installation program to modify the configuration files, press the down arrow key. Then continue to Step 5.
</PARA>
</STEP>
<STEP><PARA>If you want to modify the configuration files manually, type N and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>If you enter N, you must manually edit the AUTOEXEC.BAT and CONFIG.SYS files before you can run the NetWare/IP software. The required changes are detailed in <IXREF idref="FM11278">"Restoring Your System Files" on page 5-3</IXREF>."</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Configure MS Windows support.
</PARA>
<SUBSTEPS><STEP><PARA>To disable windows support, type N and press
<KEYCAP><Enter></KEYCAP>. Then continue to Step 6.
</PARA>
<PARA>If you subsequently install MS Windows, you must reinstall the NetWare/IP client software to configure MS Windows support.</PARA>
</STEP>
<STEP><PARA>To enable MS Windows support, press the down arrow key.
</PARA>
</STEP>
<STEP><PARA>To specify the MS Windows directory, press the down arrow key to accept the default directory; or, type the new directory path and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>If you use a network version of MS Windows, you might not have permission to modify this directory. In this case, you must enter the name of your local MS Windows directory and have your MS Windows administrator modify the files in the shared MS Windows directory as described in <IXREF idref="FM39971">"Restoring Your MS Windows Files" on page 5-8</IXREF>.</PARA>
</STEP>
<STEP><PARA>Press the down arrow key to continue to the next field.
</PARA><BEGINPAGE PAGENUM=9 ID="BP27">
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Specify whether data stored on this workstation will be backed up using NetWare Storage Management Services (SMS).
</PARA>
<SUBSTEPS><STEP><PARA>If your administrator does not use SMS to back up data for this workstation, press the down arrow key. Then continue to Step 7.
</PARA>
</STEP>
<STEP><PARA>If your NetWare administrator backs up data on this workstation using SMS, type Y and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>The installation program displays the Configure TSA for Storage Management Services (SMS) form. This form enables you to configure the workstation Target Service Agent (TSA), which the SBACKUP utility uses to transfer data between the workstation and the backup device.</PARA>
</STEP>
<STEP><PARA>Type the name of the server that provides SMS for this workstation and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Type the name of your workstation and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>If you do not want to set a SBACKUP password for the workstation, press the down arrow key to move to the next field. Or, to add an SBACKUP password for your workstation, press
<KEYCAP><Enter></KEYCAP>, type your password, and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>The installation program prompts you to retype your password.</PARA>
</STEP>
<STEP><PARA>Type the number of buffers you want available to the TSA for file transfer and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>Increasing the number of buffers increases throughput speed, but requires more workstation RAM. The default is 1 buffer, which requires 1KB of memory.</PARA>
</STEP>
<STEP><PARA>To select the workstation hard drives you want SMS to back up, press
<KEYCAP><Enter></KEYCAP> and then select the drive(s) from the Backup Drives list.
</PARA>
</STEP>
<STEP><PARA>To save the TSA configuration, press
<KEYCAP><F10></KEYCAP>.
</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>To select the driver for your network board, press
<KEYCAP><Enter></KEYCAP>.
</PARA><BEGINPAGE PAGENUM=10 ID="BP28">
<PARA>If you already have a driver loaded to memory, the installation program automatically detects the driver. If you do not have a driver loaded to memory, the installation program displays a list of network boards for you to choose from.
</PARA>
<SUBSTEPS><STEP><PARA>If you already have a driver loaded in memory, press
<KEYCAP><Enter></KEYCAP> to confirm the board detected by the installation program and then continue to Step 8.
</PARA>
</STEP>
<STEP><PARA>If you do not have a driver loaded in memory, select your board from the Network Board list.
</PARA>
</STEP>
<STEP><PARA>Specify any custom configuration settings for your board and then press
<KEYCAP><Esc></KEYCAP>.
</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Press
<KEYCAP><Enter></KEYCAP> to continue to the second NetWare/IP Client Installation form, as shown in
<IXREF idref="FMClien">Figure 3-1 on page 3-6</IXREF>.
</PARA>
</STEP>
<STEP><PARA>Specify the directory path where you want the install program to copy the TCP/IP files.
</PARA>
<SUBSTEPS><STEP><PARA>To accept the default directory path, C:\NET, press the down arrow key. Then continue to Step 10.
</PARA>
</STEP>
<STEP><PARA>To specify an alternative directory path, press
<KEYCAP><Enter></KEYCAP>, type the new path, and then press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Specify whether your workstation is using a Boot Protocol (BootP) server to obtain TCP/IP configuration parameters.
</PARA>
<PARA>If you have other TCP/IP products installed on this workstation, the installation program automatically detects your TCP/IP configuration parameters. In this case, you can press the down arrow key until you reach the Using Extended BootP Server? field and then skip to Step 17.
</PARA>
<SUBSTEPS><STEP><PARA>If your workstation is not using a BootP server to obtain TCP/IP parameters, press the down arrow key. Then continue to Step 11.
</PARA>
</STEP>
<STEP><PARA>If your workstation is using a BootP server to obtain TCP/IP parameters, type Y and press
<KEYCAP><Enter></KEYCAP>. Then skip to Step 13.
</PARA>
<PARA>The installation program removes the Client IP Address and Subnetwork Mask fields from the configuration form. These parameters are maintained by the BootP server and therefore do not need to be configured manually.</PARA>
</STEP><BEGINPAGE PAGENUM=11 ID="BP29">
</SUBSTEPS>
</STEP>
<STEP><PARA>Type the IP address of your workstation and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Type the subnetwork mask for your network and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Type the IP address of the default router for your network and then press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Type the name of the DNS domain to which this client system belongs and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Type the IP address of the first DNS name server to which this client should direct its DNS queries and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Specify the second and third DNS name servers to which this client should direct its DNS queries, pressing
<KEYCAP><Enter></KEYCAP> after each entry.
</PARA>
<PARA>A second or third DNS name server address is only required if the preceding name server(s) cannot resolve all DNS queries for the client.
</PARA>
</STEP>
<STEP><PARA>Specify whether your workstation is using a BootP server to obtain the NetWare/IP configuration parameters.
</PARA>
<SUBSTEPS><STEP><PARA>If your workstation is not using a BootP server to obtain NetWare/IP parameters, press the down arrow key. Then continue to Step 18.
</PARA>
</STEP>
<STEP><PARA>If your workstation is using a BootP server to obtain NetWare/IP parameters, type Y and press
<KEYCAP><Enter></KEYCAP>. Then skip to Step 20.
</PARA>
<PARA>The installation program removes the NetWare/IP Domain and Tunable Parameters fields from the configuration form. These parameters are maintained by the BootP server and therefore do not need to be configured manually.</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Type the fully-qualified name of your NetWare/IP domain and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA>A fully-qualified domain name ends with the dot (.) for root. For example, nwip.acme.com. is a fully-qualified domain name.
</PARA>
</STEP>
<STEP><PARA>To configure the NetWare/IP parameters, press
<KEYCAP><Enter></KEYCAP>.
</PARA><BEGINPAGE PAGENUM=12 ID="BP30">
<PARA>The installation program displays the NetWare/IP Tunable Parameters form. These parameters are optional.
</PARA>
<SUBSTEPS><STEP><PARA>Type the hostname(s), IP address(es), or subnetwork IP address(es) of up to five Domain SAP/RIP Servers (DSSes) that are closest to this workstation, pressing
<KEYCAP><Enter></KEYCAP> after each entry.
</PARA>
</STEP>
<STEP><PARA>Type the hostname(s), IP address(es), or subnetwork IP address(es) of up to five NetWare/IP servers that are closest to this workstation, pressing
<KEYCAP><Enter></KEYCAP> after each entry.
</PARA>
</STEP>
<STEP><PARA>Press
<KEYCAP><Esc></KEYCAP> to save the NetWare/IP configuration parameters.
</PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Press
<KEYCAP><Enter></KEYCAP> to install the NetWare/IP client software.
</PARA>
<PARA>The installation program begins copying files to your system. A file copy status bar indicates the percentage of the installation that is complete. The installation program lists the names of files as they are copied to your system.
</PARA>
<PARA>When the installation program displays the "The Install Utility is finished" message, the NetWare/IP client software installation has completed successfully.
</PARA>
<TIP><PARA>Before rebooting, make a backup system diskette including the unmodified versions of your AUTOEXEC.BAT and CONFIG.SYS files. If you encounter difficulty, you can use this diskette to restart the workstation.</PARA>
</TIP>
</STEP>
</PROCEDURE>
</SECT2>
<SECT2><TITLE>Configuring Other NetWare/IP Parameters</TITLE><PARA>The following NetWare/IP configuration parameters can only be modified by manually editing the NET.CFG file:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Initial DSS contact retries, which specifies the number of times the client will attempt to communicate with a given server at startup. The default is two times.</PARA>
</LISTITEM>
<LISTITEM><PARA>Retry interval, which specifies the amount of time in seconds between attempts to contact a given DSS at startup. The default is ten seconds.</PARA>
</LISTITEM><BEGINPAGE PAGENUM=13 ID="BP31">
<LISTITEM><PARA>NSQ broadcast, which specifies whether the client will use Nearest Server Query (NSQ) broadcasts to locate the nearest server. By default, the NSQ broadcasting is set to ON.</PARA>
</LISTITEM>
<LISTITEM><PARA>NetWare/IP 1.1 compatibility, which specifies whether this client can access NetWare/IP 1.1. By default, NetWare/IP 1.1 compatibility is set to OFF.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>You can modify these parameters by using any text editor to edit the corresponding entry in the NET.CFG file. The following examples illustrate how to modify each of these parameters.</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>To modify the Initial DSS Contact Retries parameter from the default of two retries to five retries, edit the AUTORETRIES line in the [NWIP] section of your NET.CFG file as follows:</PARA>
<PARA><USERINPUT>AUTORETRIES 5</USERINPUT></PARA>
</LISTITEM>
<LISTITEM><PARA>To modify the Retry Interval parameter from the default of ten seconds to 20 seconds, edit the AUTORETRY SECS line in the [NWIP] section of your NET.CFG file as follows:</PARA>
<PARA><USERINPUT>AUTORETRY SECS 20</USERINPUT></PARA>
</LISTITEM>
<LISTITEM><PARA>To turn off NSQ Broadcasting, edit the NSQ_BROADCAST line in the [NWIP] section of your NET.CFG file as follows:</PARA>
<PARA><USERINPUT>NSQ_BROADCAST OFF</USERINPUT></PARA>
</LISTITEM>
<LISTITEM><PARA>To turn on NetWare/IP 1.1 compatibility, edit the NWIP1_1 COMPATIBILITY line in the [NWIP] section of your NET.CFG file as follows:</PARA>
<PARA><USERINPUT>NWIP1_1 COMPATIBILITY ON</USERINPUT></PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>All other NetWare/IP parameters are configured during installation. However, you can modify any of the parameter values you specified during installation by editing the NET.CFG file.</PARA>
</SECT2>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="4"><TITLE><BEGINPAGE PAGENUM=1 ID="BP32"><XMARK id="FMRunni">Running the NetWare/IP Client Software</TITLE><PARA>After you have successfully installed the NetWare/IP<SUPERSCRIPT>TM</SUPERSCRIPT> software on your workstation, you are ready to log in to the network. Logging in is the procedure that provides your client workstation access to network resources such as network directories, printers, and applications.</PARA>
<PARA>This chapter includes the following sections:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><IXREF idref="FM19179">Before You Begin </IXREF></PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM13532">Logging In from DOS </IXREF></PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM39050">Logging In from MS* Windows </IXREF></PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM21881">Troubleshooting the NetWare/IP Client Software </IXREF></PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM21233">Connecting to Servers in Other NetWare/IP Domains </IXREF></PARA>
</LISTITEM>
</ITEMIZEDLIST>
<SECT1><TITLE><XMARK id="FM19179">Before You Begin</TITLE><PARA>Before you run your NetWare/IP software for the first time, you should make a backup system diskette including the unmodified versions of your AUTOEXEC.BAT and CONFIG.SYS files. If you encounter difficulty, you can then use this diskette to restart your workstation. </PARA>
<PARA>The following sections contain additional information you may need to know before you run the NetWare/IP client software.</PARA>
<SECT2><TITLE>Considerations for Workstations Upgraded from NetWare 3.11 or Earlier</TITLE><PARA>If you are upgrading to NetWare/IP from NetWare 3.11 or earlier software, you may need to delete or comment out any commands in your AUTOEXEC.BAT that conflict with the newly installed software. </PARA>
<BEGINPAGE PAGENUM=2 ID="BP33"><PARA>If your AUTOEXEC.BAT file or other batch files run from AUTOEXEC.BAT contain commands to run any of the following programs, you must delete or comment out the commands:</PARA>
<SIMPLELIST><MEMBER>LSL.COM</MEMBER>
<MEMBER>Network board driver (for example, NE2000.COM<SUPERSCRIPT>TM</SUPERSCRIPT>)
</MEMBER>
<MEMBER>IPXODI.COM
</MEMBER>
<MEMBER>NETX.COM
</MEMBER>
<MEMBER>IPX.COM
</MEMBER>
</SIMPLELIST>
</SECT2>
<SECT2><TITLE>Considerations for Workstations Running LAN WorkPlace or LAN WorkGroup</TITLE><PARA>If your workstation runs LAN WorkPlace or LAN WorkGroup, make sure your AUTOEXEC.BAT file runs only the STARTNET.BAT file created by NetWare/IP installation, instead of LANWP.BAT or LANWG.BAT. STARTNET.BAT is illustrated and explained in <IXREF idref="FM24750">Figure 5-4 on page 5-7</IXREF>. If you have customized your LANWP.BAT or LANWG.BAT file, you can incorporate your customizations into STARTNET.BAT.</PARA>
</SECT2>
<SECT2><TITLE>Considerations for Workstations Running PCNFS Applications</TITLE><PARA>If your workstation runs a PCNFS application, you must configure all drive mappings before loading the NetWare/IP VLM<SUPERSCRIPT>TM</SUPERSCRIPT> programs.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM13532">Logging In from DOS</TITLE><PARA>When you restart your workstation after installing the NetWare/IP client software, the NetWare/IP client software runs automatically. You can then log in to the network using the following procedure:</PARA>
<PROCEDURE><STEP><PARA>Change to the first network drive by typing</PARA>
<PARA><USERINPUT>F:</USERINPUT><KEYCAP><Enter></KEYCAP></PARA>
</STEP>
<STEP><PARA>Log in to the network in one of the following ways:
</PARA>
<SUBSTEPS><STEP><PARA>If your name context is set in your NET.CFG file, log in to the Directory tree using only your username by typing
</PARA>
<PARA><USERINPUT>LOGIN</USERINPUT> <REPLACEABLE>username</REPLACEABLE><KEYCAP><Enter></KEYCAP></PARA>
<BEGINPAGE PAGENUM=3 ID="BP34"><PARA>For example, type</PARA>
<PARA><USERINPUT>LOGIN LANDREW</USERINPUT><KEYCAP><Enter></KEYCAP></PARA>
</STEP>
<STEP><PARA>To log in to a specific server, type
</PARA>
<PARA><USERINPUT>LOGIN</USERINPUT> <REPLACEABLE>servername</REPLACEABLE><USERINPUT>/</USERINPUT><REPLACEABLE>username</REPLACEABLE><KEYCAP><Enter></KEYCAP></PARA>
<PARA>For example, type</PARA>
<PARA><USERINPUT>LOGIN JUPITER/LANDREW</USERINPUT><KEYCAP><Enter></KEYCAP></PARA>
</STEP>
</SUBSTEPS>
</STEP>
<STEP><PARA>Type your password if required.
</PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE><XMARK id="FM39050">Logging In from MS* Windows</TITLE><PARA>You can use the NetWare User Tools in MS Windows to log in to a NetWare/IP or NetWare server.</PARA>
<NOTE><PARA>The NetWare User Tools Login option authenticates you to NetWare Directory Services<SUPERSCRIPT>TM</SUPERSCRIPT> (NDS<SUPERSCRIPT>TM</SUPERSCRIPT>) or to a NetWare server. It does not run a login script for your client workstation. If you want to run a login script, you must log in from the DOS command line using the LOGIN utility before loading MS Windows.</PARA>
</NOTE>
<PARA>Use the following procedure to log in to a server from MS Windows:</PARA>
<PROCEDURE><STEP><PARA>Open the NetWare Tools program group and double-click the NetWare User Tools icon to load the NetWare tools.</PARA>
</STEP>
<STEP><PARA>Click the server icon.
</PARA>
<PARA>The NetWare Connections window displays available resources.
</PARA>
</STEP>
<STEP><PARA>Click on the name of the server to which you want to log in.
</PARA>
</STEP>
<STEP><PARA>Click Login.
</PARA>
<PARA>Click the Help button for more details.
</PARA>
</STEP>
<STEP><PARA>Type your login name and password.
</PARA>
</STEP>
<STEP><PARA>Click OK.
</PARA>
</STEP>
</PROCEDURE>
<PARA><IXREF idref="FM36825">Figure 4-1</IXREF> illustrates how to use the NetWare User Tools to log in to your server.</PARA>
<BEGINPAGE PAGENUM=4 ID="BP35"><FIGURE LABEL="4-1"><TITLE><XMARK id="FM36825">NetWare Tools</TITLE><GRAPHIC FILEREF="vlm.tif"></GRAPHIC>
</FIGURE>
<PARA></PARA>
</SECT1><BEGINPAGE PAGENUM=5 ID="BP36">
<SECT1><TITLE><XMARK id="FM21881">Troubleshooting the NetWare/IP Client Software</TITLE><PARA>The following sections provide information to help you troubleshoot your NetWare/IP software.</PARA>
<SECT2><TITLE>Running NetWare/IP in Verbose Mode</TITLE><PARA>If you have problems running the NetWare/IP software on your workstation, you can use the verbose switch (/v) to display information about the status of the network. </PARA>
<PARA>To run NetWare/IP using the verbose switch, type the following command at the DOS prompt:</PARA>
<LITERALLAYOUT><USERINPUT>nwip/v
</USERINPUT></LITERALLAYOUT>
<PARA>The workstation then loads NWIP.EXE and displays the following diagnostic information:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>The version of NetWare/IP software this client is using.</PARA>
</LISTITEM>
<LISTITEM><PARA>The address of the DSS this client is using to obtain global parameters and NetWare/IP server location. This line also indicates the number of times the client has attempted to contact this DSS with no response.</PARA>
</LISTITEM>
<LISTITEM><PARA>The address of the NetWare/IP server this client is using to obtain network service information. This line also indicates the number of times the client has attempted to contact this NetWare/IP server with no response. </PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>For example, when you run NetWare/IP using the verbose switch, the workstation displays the following information:</PARA>
<LITERALLAYOUT><COMPUTEROUTPUT>It is a post NWIP v1.1 client TSR</COMPUTEROUTPUT></LITERALLAYOUT>
<LITERALLAYOUT><COMPUTEROUTPUT>*DSS address: 1.2.3.4 NO_ANS Count: 0 *NWIP Server address: 1.2.3.5 NO_ANS Count: 0</COMPUTEROUTPUT><BEGINPAGE PAGENUM=6 ID="BP37"></LITERALLAYOUT>
</SECT2>
<SECT2><TITLE>Configuring Other Frame Types</TITLE><PARA>Frame types determine how packets of network data are formatted on different LANs. Ethernet, token ring, ARCnet, and other LANs use different formats. The TCP/IP and IPX protocols also require different frame types in some instances.</PARA>
<PARA>Installing the NetWare/IP client software configures the correct frame type for most TCP/IP networks, which are supported automatically. However, if your network uses a frame type that is not automatically supported, the wrong frame type may be configured. In this case, when you run the NetWare/IP client software, your system displays the following error message:</PARA>
<LITERALLAYOUT><COMPUTEROUTPUT>Error registering protocol IDs</COMPUTEROUTPUT></LITERALLAYOUT>
<PARA>If this happens, you must specify an alternative frame type.</PARA>
<PARA>The NetWare/IP installation program configures one of the following supported frame types as appropriate for your network board:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Ethernet: ETHERNET_II or ETHERNET_SNAP</PARA>
</LISTITEM>
<LISTITEM><PARA>Token ring: TOKEN-RING_SNAP</PARA>
</LISTITEM>
<LISTITEM><PARA>ARCnet: NOVELL_RX-NET</PARA>
</LISTITEM>
<LISTITEM><PARA>PCN or PCN II: IBM_PCN2_SNAP</PARA>
</LISTITEM>
<LISTITEM><PARA>FDDI: FDDI_SNAP</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>If your TCP/IP network uses a different frame type, you can modify the NET.CFG file in your NetWare/IP client directory (C:\NWCLIENT by default). You network administrator can let you know if this change is needed.</PARA>
<PARA>To enable support for a different frame type, you change the Frame line in NET.CFG under the Link Driver heading for your network board driver (<REPLACEABLE>drivername</REPLACEABLE>), and add a Protocol statement including the protocol name, hexadecimal ID number, and frame type. For example, to enable the token-ring frame type, you would add the following lines to the NET.CFG file: </PARA>
<BEGINPAGE PAGENUM=7 ID="BP38"><LITERALLAYOUT><COMPUTEROUTPUT>Link Driver <REPLACEABLE>drivername </REPLACEABLE>FRAME TOKEN-RING PROTOCOL IP E0 TOKEN-RING</COMPUTEROUTPUT></LITERALLAYOUT>
<PARA>Network board drivers from other manufacturers may support additional frame types. Consult the documentation accompanying your network board driver for information about the NET.CFG changes required for these frame types.</PARA>
<PARA>See <IXREF idref="FM38967">Figure 5-3 on page 5-6</IXREF> for a complete example NET.CFG file.</PARA>
</SECT2>
<SECT2><TITLE>Common Error Messages and Solutions</TITLE><PARA>See <IXREF idref="FM89185">Appendix B, "Error Messages,"</IXREF> for a complete list of client error messages and solutions.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM21233">Connecting to Servers in Other NetWare/IP Domains</TITLE><PARA>When you log in to your NetWare/IP server or network, you can display and access the NetWare servers in your NetWare/IP domain. Usually this domain includes all of your company's network. NetWare/IP also allows you to map drives to servers in other NetWare/IP domains, called <EMPHASIS>remote domains</EMPHASIS>. For example, you might want to connect to a NetWare/IP server at another company on the Internet. </PARA>
<PARA>To let you connect to remote domains that are accessible from your network, NetWare/IP provides the NWIPMAP utility. You need the following three pieces of information to use this utility:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>The fully-qualified domain name of the remote NetWare/IP domain.</PARA>
</LISTITEM>
<LISTITEM><PARA>The name of the NetWare/IP server in the remote domain.</PARA>
</LISTITEM>
<LISTITEM><PARA>The volume (and optionally directory) on the remote server.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>The server in the remote NetWare/IP domain must be accessible through DNS, and you must have permission to attach to the server.</PARA>
<BEGINPAGE PAGENUM=8 ID="BP39"><SECT2><TITLE>Using the NWIPMAP Utility</TITLE><PARA>The NWIPMAP utility works in a manner similar to the NetWare MAP command and has the same command format, except that you include the name of the remote NetWare/IP domain:</PARA>
<LITERALLAYOUT><USERINPUT>NWIPMAP <REPLACEABLE>drive</REPLACEABLE>:=<REPLACEABLE>servername</REPLACEABLE>\<REPLACEABLE>vol</REPLACEABLE>:[ <REPLACEABLE>path</REPLACEABLE> ]@<REPLACEABLE>domain</REPLACEABLE>
</USERINPUT></LITERALLAYOUT>
<PARA>For <REPLACEABLE>domain</REPLACEABLE>, substitute the fully-qualified domain name of the remote NetWare/IP domain. For example, the following command maps drive G: to a server named VENUS in NetWare/IP domain nwip.theircorp.com.:</PARA>
<LITERALLAYOUT><COMPUTEROUTPUT>NWIPMAP G:=VENUS\SYS:\PUBLIC@NWIP<USERINPUT>.</USERINPUT>THEIRCORP<USERINPUT>.</USERINPUT>COM<USERINPUT>.</USERINPUT></COMPUTEROUTPUT></LITERALLAYOUT>
<PARA>Once you have connected to a remote server using NWIPMAP, you can make the mapped drive the current drive and access services provided by that server. </PARA>
<PARA>Continuing the previous example, the following sequence of commands would list the servers available in the nwip.theircorp.com NetWare/IP domain, and attach to server MARS in that domain:</PARA>
<LITERALLAYOUT><COMPUTEROUTPUT>G: NLIST ATTACH MARS\GUEST</COMPUTEROUTPUT></LITERALLAYOUT>
<PARA>From the remote domain, you can execute any DOS and MS Windows commands. You can also run any NetWare/IP utility that does not use SAP/RIP broadcasting. This means that you can use file services and remote management utilities such as NLIST and RCONSOLE because they do not rely on SAP/RIP broadcasting. You cannot however, use print services such as PSERVER or PCONSOLE or the MAP utility because these utilities rely on SAP/RIP broadcasting.</PARA>
</SECT2>
<SECT2><TITLE>Mapping a Drive to a Remote NetWare/IP Domain</TITLE><PARA>Use the following procedure to map a drive to a remote NetWare/IP domain:</PARA>
<PROCEDURE><STEP><PARA>Type the following command:</PARA>
<PARA><USERINPUT>NWIPMAP</USERINPUT>
<REPLACEABLE>drive</REPLACEABLE><USERINPUT>:=</USERINPUT><REPLACEABLE>servername</REPLACEABLE><USERINPUT>\</USERINPUT><REPLACEABLE>vol</REPLACEABLE><USERINPUT>:</USERINPUT>[
<REPLACEABLE> path </REPLACEABLE>]
<USERINPUT>@</USERINPUT><REPLACEABLE>domain</REPLACEABLE><KEYCAP><Enter></KEYCAP></PARA><BEGINPAGE PAGENUM=9 ID="BP40">
</STEP>
<STEP><PARA>Type your username and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Type your password and press
<KEYCAP><Enter></KEYCAP>.
</PARA>
<PARA></PARA>
</STEP>
</PROCEDURE>
</SECT2>
<SECT2><TITLE>NWIPMAP Limitations</TITLE><PARA>NWIPMAP has the following limitations:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>You can use NWIPMAP to connect to more than one remote NetWare/IP domain at a time. However, you can list and access other resources in only one remote domain at a time, the most recent one to which you established an NWIPMAP connection.</PARA>
</LISTITEM>
<LISTITEM><PARA>The NetWare/IP requirement that IPX network numbers must be unique across internetwork connections applies to NWIPMAP connections as well. Furthermore, server names must be unique among all NetWare/IP domains to which you connect.</PARA>
</LISTITEM>
<LISTITEM><PARA>All NetWare/IP domains to which you connect must use the same TCP/UDP port numbers.</PARA>
</LISTITEM>
<LISTITEM><PARA>NWIPMAP provides file access only. Other resources in the remote NetWare/IP domain, such as printers, are not available.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="5"><TITLE><BEGINPAGE PAGENUM=1 ID="BP41"><XMARK id="FMRemov">Removing the NetWare/IP Client Software</TITLE><PARA>This chapter provides procedures for removing the NetWare/IP software from your client worksatation. To remove the software, you must complete the following tasks:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Delete the NetWare/IP files</PARA>
</LISTITEM>
<LISTITEM><PARA>Restore your system files</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<SECT1><TITLE>Removing the Software</TITLE><PARA>To remove the NetWare/IP software from your workstation, take note of the following warnings and then do the following:</PARA>
<WARNING><PARA>Before you delete any files, make sure you have a complete backup copy of your system. If you inadvertently delete files that are needed by another program, you can restore them from the backup.</PARA>
<PARA>If your workstation previously ran NetWare IPX software and you want to restore that software to operation, do not delete any files from your NetWare IPX client directory or your MS Windows directory. If you deleted the file NWTOOLS.EXE from your MS Windows directory, restore a backup copy of this file if you want to restore the MS Windows tools to operation.</PARA>
<PARA>If your workstation runs LAN WorkPlace or LAN WorkGroup, do not delete any files from your \NET or MS Windows directories.</PARA>
</WARNING>
<PROCEDURE><STEP><PARA>Delete the NetWare/IP client directory, which is C:\NWCLIENT by default.</PARA>
<PARA>Saving a backup copy of the NET.CFG file stored in this directory is recommended.
</PARA>
</STEP>
<STEP><PARA>Delete the TCP/IP directory, which is C:\NET by default.
</PARA><BEGINPAGE PAGENUM=2 ID="BP42">
</STEP>
<STEP><PARA>Delete the following from the Windows directory.
</PARA><INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="12*">
<COLSPEC colname=2 colwidth="12*">
<TBODY><ROW><ENTRY colname=1><PARA>NOVELL.BMP</PARA></ENTRY>
<ENTRY colname=2><PARA>NWADMIN.INI</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NOVLOGO1.BMP</PARA></ENTRY>
<ENTRY colname=2><PARA>NWRCON.PIF</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NW.GRP</PARA></ENTRY>
<ENTRY colname=2><PARA></PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
</STEP>
<STEP><PARA>Delete the following from the Windows\System directory.
</PARA><INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="12*">
<COLSPEC colname=2 colwidth="12*">
<TBODY><ROW><ENTRY colname=1><PARA>NETWARE.DRV</PARA></ENTRY>
<ENTRY colname=2><PARA>NWUSER.EXE</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NETWARE.HLP</PARA></ENTRY>
<ENTRY colname=2><PARA>PNW.DLL</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWCALLS.DLL</PARA></ENTRY>
<ENTRY colname=2><PARA>RES_SUPP.DLL</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWGDI.DLL</PARA></ENTRY>
<ENTRY colname=2><PARA>TASKID.COM</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWIPWIN.EXE</PARA></ENTRY>
<ENTRY colname=2><PARA>TBMI2.COM</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWIPXSSPX.DLL</PARA></ENTRY>
<ENTRY colname=2><PARA>TLI_SPX.DLL</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWLOCALE.DLL</PARA></ENTRY>
<ENTRY colname=2><PARA>TLI_TCP.DLL</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWNET.DLL</PARA></ENTRY>
<ENTRY colname=2><PARA>TLI_WIN.DLL</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWPOPUP.EXE</PARA></ENTRY>
<ENTRY colname=2><PARA>VIPX.386</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NWPSRV.DLL</PARA></ENTRY>
<ENTRY colname=2><PARA>VNETWARE.386</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
</STEP>
<STEP><PARA>Delete the following from the Windows\NLS directory.
</PARA><INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="12*">
<COLSPEC colname=2 colwidth="12*">
<TBODY><ROW><ENTRY colname=1><PARA>1252_UNI.001</PARA></ENTRY>
<ENTRY colname=2><PARA>UNI_COL.001</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>UNI_1252.001</PARA></ENTRY>
<ENTRY colname=2><PARA>UNI_MON.001</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
</STEP>
<STEP><PARA>Delete the following from the Windows\NLS\ENGLISH directory.
</PARA><INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="12*">
<COLSPEC colname=2 colwidth="12*">
<TBODY><ROW><ENTRY colname=1><PARA>NETWARE.HLP</PARA></ENTRY>
<ENTRY colname=2><PARA>TASKID.MSG</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NETWARER.DRV</PARA></ENTRY>
<ENTRY colname=2><PARA>TBMI2.MSG</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<BEGINPAGE PAGENUM=3 ID="BP43"><PARA>For a shared MS Windows, the server administrator copies these files to the MS Windows directory on the server. They do not have to be deleted from your workstation.
</PARA>
</STEP>
<STEP><PARA>Restore the backup (.BNW) copies of the following system files:
</PARA><INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="12*">
<COLSPEC colname=2 colwidth="12*">
<TBODY><ROW><ENTRY colname=1><PARA>AUTOEXEC.BAT</PARA></ENTRY>
<ENTRY colname=2><PARA>PROGMAN.INI</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>CONFIG.SYS</PARA></ENTRY>
<ENTRY colname=2><PARA>SYSTEM.INI</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NET.CFG</PARA></ENTRY>
<ENTRY colname=2><PARA>WIN.INI</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>STARTNET.BAT</PARA></ENTRY>
<ENTRY colname=2><PARA></PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<PARA>You have backup copies of NET.CFG and STARTNET.BAT only if you were previously running NetWare IPX client software.
</PARA>
<PARA>If you have modified your system files in other ways since installing the NetWare/IP client, you can remove the NetWare/IP information from these files manually instead of restoring the backups. The sections that follow provide the information you need to edit these files.
</PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE><XMARK id="FM11278">Restoring Your System Files</TITLE><PARA>If you have changed your system files since installing the NetWare/IP client software, you might prefer to delete the NetWare/IP changes rather than restoring the backup copies. The sections below describe the changes you need to make to your system files when you remove the NetWare/IP client software.</PARA>
<SECT2><TITLE>AUTOEXEC.BAT</TITLE><PARA><IXREF idref="FM23426">Figure 5-1</IXREF> illustrates the changes made to the AUTOEXEC.BAT file by the installation program.</PARA>
<BEGINPAGE PAGENUM=4 ID="BP44"><FIGURE LABEL="5-1"><TITLE><XMARK id="FM23426">Example AUTOEXEC.BAT File After NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="autoexec.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=5 ID="BP45">
</SECT2>
<SECT2><TITLE>CONFIG.SYS</TITLE><PARA><IXREF idref="FM21849">Figure 5-2</IXREF> illustrates the changes made to the CONFIG.SYS file by the installation program.</PARA>
<FIGURE LABEL="5-2"><TITLE><XMARK id="FM21849">Example CONFIG.SYS File After NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="config.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=6 ID="BP46">
</SECT2>
<SECT2><TITLE>NET.CFG</TITLE><PARA><IXREF idref="FM38967">Figure 5-3</IXREF> illustrates the contents of the NET.CFG file that is created or modified by the installation program.</PARA>
<FIGURE LABEL="5-3"><TITLE><XMARK id="FM38967">Example NET.CFG File After NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="netcfg.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=7 ID="BP47">
<NOTE><PARA>If you are using a BOOTP server, the ip_address and ip_netmask lines are not included in the file.</PARA>
</NOTE>
<PARA>Other Novell software packages also make use of the NET.CFG file. If you have customized your NET.CFG file, additional entries may be present. Refer to the <CITETITLE>Workstation Basics and Installation</CITETITLE><CITETITLE> manual for NetWare 4</CITETITLE> or the documentation for the software that is using NET.CFG for information about custom changes to this file.</PARA>
</SECT2>
<SECT2><TITLE>STARTNET.BAT</TITLE><PARA><IXREF idref="FM24750">Figure 5-4</IXREF> illustrates the STARTNET.BAT file that is created or modified by the installation program.</PARA>
<FIGURE LABEL="5-4"><TITLE><XMARK id="FM24750">Example STARTNET.BAT File After NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="startnet.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=8 ID="BP48">
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM39971">Restoring Your MS Windows Files</TITLE><PARA>The NetWare/IP installation utility makes several changes to the MS Windows configuration files in your MS Windows directory, saving your original files in backup copies with the .BNW extension. These files are also used and modified by other MS Windows applications and by MS Windows itself. </PARA>
<PARA>The sections that follow describe the specific changes made to support NetWare/IP.</PARA>
<SECT2><TITLE>WIN.INI</TITLE><PARA><IXREF idref="FM36728">Figure 5-5</IXREF> illustrates the changes made to the WIN.INI file.</PARA>
<FIGURE LABEL="5-5"><TITLE><XMARK id="FM36728">Modifications to WIN.INI by NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="winini.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=9 ID="BP49">
</SECT2>
<SECT2><TITLE>SYSTEM.INI</TITLE><PARA><IXREF idref="FM14839">Figure 5-6</IXREF> illustrates the changes made to the SYSTEM.INI file.</PARA>
<FIGURE LABEL="5-6"><TITLE><XMARK id="FM14839">Modifications to SYSTEM.INI by NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="sysini.tif"></GRAPHIC>
</FIGURE><BEGINPAGE PAGENUM=10 ID="BP50">
</SECT2>
<SECT2><TITLE>PROGMAN.INI</TITLE><PARA><IXREF idref="FM26871">Figure 5-7</IXREF> illustrates the changes made to the PROGMAN.INI file.</PARA>
<FIGURE LABEL="5-7"><TITLE><XMARK id="FM26871">Modifications to PROGMAN.INI by NetWare/IP Client Software Installation</TITLE><GRAPHIC FILEREF="progman.tif"></GRAPHIC>
</FIGURE>
</SECT2>
</SECT1>
</CHAPTER>
<APPENDIX LABEL="A"><TITLE><BEGINPAGE PAGENUM=1 ID="BP51"><XMARK id="FM70650">Planning Worksheets</TITLE><PARA>This appendix provides the NetWare/IP<SUPERSCRIPT>TM</SUPERSCRIPT> Client Worksheet. When completed, this worksheet provides all the information you need to install and configure your NetWare/IP client system. Have your NetWare/IP administrator complete this worksheet before you begin your installation.</PARA>
<PARA>Short descriptions of each parameter are included on the worksheet. If you need additional information about a parameter while you are installing the NetWare/IP client software, you can press <F1> to display a help screen.</PARA>
<BEGINPAGE PAGENUM=3 ID="BP52"><GRAPHIC FILEREF="nwip_w4.tif"></GRAPHIC>
</APPENDIX>
<APPENDIX LABEL="B"><TITLE><BEGINPAGE PAGENUM=47 ID="BP53"><XMARK id="FM89185">Error Messages</TITLE><PARA>This appendix provides essential information for most error messages that you might encounter when using the NetWare/IP product. This appendix presents an alphabetical listing of error messages that is followed by an explanation of error codes. Each error message contains the following information:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Explanation of the cause of the error.</PARA>
</LISTITEM>
<LISTITEM><PARA>What action you should take to correct the error.</PARA>
</LISTITEM>
<LISTITEM><PARA>Severity of the error. The severity of the error message can be one of the following:</PARA>
</LISTITEM>
<LISTITEM><PARA>ERROR: The system might or might not work properly. The problem should be fixed before you continue.</PARA>
</LISTITEM>
<LISTITEM><PARA>WARNING: The system is still functioning, and you can work around the problem. Usually this indicates that the system cannot find something, such as a file.</PARA>
</LISTITEM>
<LISTITEM><PARA>INFORMATIONAL: Information about the status of NetWare/IP.</PARA>
</LISTITEM>
<LISTITEM><PARA>DEBUG: Detailed information about NetWare/IP operation. These messages are used by the technical support staff and should not normally display.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<MSGSET><MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>An invalid entry was found on line n of the configuration file. Entry <entry name> ignored.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>An invalid entry was found in the IPX section of your NET.CFG file.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=48 ID="BP54">
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Enter a valid parameter value for the parameter on the specified line of your NET.CFG file.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot allocate memory for building DSS list.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>Memory allocation failure.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Unload any unused TSRs to free up some memory.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot contact any of the DSSes to get the SOA record.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client was able to locate a DSS using a DNS query but was unable to obtain an SOA record from the DSS.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Have your NetWare/IP administrator check that DNS and DSS are properly configured and loaded.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot find a NetWare/IP client to unload.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>You tried to unload the NetWare/IP client software but it is not loaded.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>None required.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot get NWIP parameters from DSS.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client located a DSS but was unable to obtain the global NetWare/IP configuration parameters.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Have your NetWare/IP administrator check the primary DSS configuration.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=49 ID="BP55">
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot obtain global DSSes by sending DNS queries. Check DNS client (resolver) configuration.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client cannot locate any DSSes in the DNS hierarchy by querying DNS.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Have your NetWare/IP administrator add name server (ns) resource records to the DNS database for all DSSes servicing your NetWare/IP domain.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot open local parameters file NWIPPARM.NOV for writing.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP cannot open or create the local NWIPPARM.NOV parameter file for writing.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Make sure your workstation is not out of disk space. Check to make sure that the permissions are set properly for your files and directories.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot pass NWIP Initialization, NWIP.EXE is not loaded!</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP is unable to initialize. This may be due to errors encountered in nwipinit.exe.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Fix any problems reported by nwipinit.exe.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot read from local parameters file NWIPPARM.NOV.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP cannot read from the local NWIPPARM.NOV parameter file.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Check the file attributes for NWIPPARM.NOV.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=50 ID="BP56">
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot unload NetWare/IP because another program has been loaded above it. Unload the other program or programs and try again.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>There are other applications or TSRs loaded that are using NetWare/IP.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Unload the other applications or TSRs before unloading NetWare/IP.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot use local NetWare/IP parameters because the NWIP Domain has changed.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client was unable to obtain the global NetWare/IP parameters from the NetWare/IP server or DSS and attempted to start up using its local copy of the global parameters. However, the NetWare/IP domain name has changed since the last time the client was running. </PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Have your NetWare/IP administrator verify that the NetWare/IP domain name has changed. If the NetWare/IP domain name has changed, the administrator must restart the primary DSS, all secondary DSSes, and all NetWare/IP servers. You must then reboot your client system.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Cannot write to local parameters file NWIPPARM.NOV.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP cannot open or create the local NWIPPARM.NOV parameter file for writing.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>Make sure your workstation is not out of disk space. </PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Could not contact any DSS. Using local copy of NetWare/IP parameters.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client cannot locate a DSS and is therefore using its local copy of the NetWare/IP parameters to boot.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Have your NetWare/IP administrator check the DSS and DNS server configurations. Check that your resolv.cfg file is configured properly.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=51 ID="BP57">
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>DNS name defined in net.cfg cannot be resolved.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The DNS hostname specified for the PREFERRED_DSS or NEAREST_NWIP_SERVER parameter in the [NWIP] section of your net.cfg file cannot be resolved. As a result, the entry will be ignored.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Make sure that the DNS hostname specified in the net.cfg file are spelled correctly.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Error in getting NWIP parameters, <EMPHASIS>n</EMPHASIS> bytes received.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client erroneously received NetWare/IP parameters from the DSS.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Call Novell Technical Support.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Failed to invoke nwipinit.exe, NWIP aborted.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP cannot find nwipinit.exe in the directory where nwip.exe is loaded.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Make sure nwipinit.exe is in the same directory as nwip.exe.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>FATAL: Cannot get NWIP Domain Name, check net.cfg file!</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The NWIP_DOMAIN_NAME parameter is not defined in your net.cfg file.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Configure the NWIP_DOMAIN_NAME parameter in the [NWIP] section of your net.cfg file with the name of your NetWare/IP domain.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>FATAL: TCP/IP is not loaded.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO><BEGINPAGE PAGENUM=52 ID="BP58">
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>There is no TCP/IP stack loaded on this machine.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Load the TCP/IP stack before loading NWIP.EXE.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>FATAL: Unknown error resulting from get local IP address.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP cannot obtain your system's IP address from the TCP/IP stack.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Call Novell Technical Support.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Invalid "BIND" statement on line n of the configuration file. Bind is not applicable to NWIP. Entry was ignored.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>A BIND statement was found in the IPX section of your NET.CFG file.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Remove the BIND statement from your NET.CFG file.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Invalid command line option was specified: <option></PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>An invalid command line option was specified while loading NWIP.EXE.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Check the commands that execute while loading NetWare/IP.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Local DSS at this IP address is not responding. Its entry is dropped.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>A local DSS specified as a preferred DSS for your workstation is not responding.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=53 ID="BP59">
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Check the PREFERRED_DSS parameter entry to ensure that the IP address entered is correct. Have your NetWare/IP administrator check that the DSS is properly configured and loaded.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Maximum number of stacks already loaded. Either unload an existing stack or increase the maximum by adding a "MAX STACKS" entry to the "LINK SUPPORT" section of the NET.CFG file.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The maximum number of stacks specified for the MAX_STACKS parameter in the Link Support section of your NET.CFG file.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Increase the MAX STACKS parameter value in the Link Support section of your NET.CFG file.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Message file is invalid. Program load aborted.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The specified message file is invalid.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Examine the reported path and name of the message file and then fix it.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Missing or invalid IPATCH values were specified on line <EMPHASIS>n</EMPHASIS> of the configuration file. Entry was ignored.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The IPATCH value specified in your NET.CFG file is invalid.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Correct the IPATCH value specified in your NET.CFG file.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>Missing or invalid value for <EMPHASIS>x</EMPHASIS> parameter was specified on line <EMPHASIS>n</EMPHASIS> of the configuration file.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>A parameter value in your NET.CFG file is missing or incorrect.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=54 ID="BP60">
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Examine the parameter on line <EMPHASIS>n</EMPHASIS> of the NET.CFG file. Add a value or correct the existing value.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>NetWare/IP cannot be unloaded because interrupt <EMPHASIS>n</EMPHASIS> is owned by another program. Unload the other program and then unload NetWare/IP.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP cannot be unloaded because it cannot unhook the specified interrupt, which is currently hooked by another program.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Unload the program that hooks the specified interrupt and then try to unload NetWare/IP again.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>NetWare/IP cannot be unloaded because the installed NetWare/IP or IPXODI is a different version than this NetWare/IP module.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The memory resident NWIP or IPX is different than the NWIP.EXE in the load path.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Find the NWIP.EXE that matches the memory-resident NWIP and then try unloading again.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>NetWare/IP client is loaded but NOT ready since TCP/IP is NOT available.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Informational</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NetWare/IP is running in a deferred TCP/IP environment, which could be mobile or VxD/DLL-based TCP/IP.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>None required.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>NWIPINIT cannot be executed by itself! Execute NWIP.EXE now.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>NWIPINIT.EXE cannot be loaded and executed alone. It is implicitly loaded and executed by NWIP.EXE.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=55 ID="BP61">
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Run NWIP.EXE.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>The LSL is not loaded. Please load the LSL then NetWare/IP.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>Your system attempted to load NWIP.EXE before loading LSL.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Load LSL.COM now.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>The loaded LSL is too old. LSL.COM must be v1.20 or higher.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIP.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>Your system is using a version of LSL.COM prior to version 1.20.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Load v. 1.20 or higher of LSL.COM.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>There is no local copy of the NetWare/IP parameters.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Warning</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The client was unable to obtain the global NetWare/IP parameters from the NetWare/IP server or DSS and attempted to start up using its local copy of the global parameters. However, the client was unable to find the configuration information locally.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Have your NetWare/IP administrator check that DNS, DSS, and NetWare/IP are running and are configured properly.</PARA>
</MSGEXPLAN>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>WARNING: Cannot resolve NWIP Domain <domain name>, check DNS/DSS configuration!</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>NWIPINIT.EXE</MSGORIG>
<MSGLEVEL>Error</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The specified NetWare/IP domain is not resolvable using DNS queries.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Make sure the NetWare/IP domain name is specified correctly in the [NWIP] section of your net.cfg file. Have your system administrator check the configuration of the DSS and DNS servers.</PARA>
</MSGEXPLAN><BEGINPAGE PAGENUM=56 ID="BP62">
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA></PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
</MSGENTRY>
<MSGENTRY><MSG><MSGMAIN><MSGTEXT><PARA>445: Fatal IO error (<err_num>) <err_msg>, occurred on <hostname> session <sess_num>.</PARA>
</MSGTEXT>
</MSGMAIN>
</MSG>
<MSGINFO><MSGORIG>XCONSOLE</MSGORIG>
<MSGLEVEL>ERROR</MSGLEVEL>
</MSGINFO>
<MSGEXPLAN><TITLE>Explanation: </TITLE><PARA>The <err_msg> describes the unexpected error which occurred.</PARA>
</MSGEXPLAN>
<MSGEXPLAN><TITLE>Action: </TITLE><PARA>Reestablish the XConsole session.</PARA>
</MSGEXPLAN>
</MSGENTRY>
</MSGSET>
</APPENDIX>
<GLOSSARY><TITLE><BEGINPAGE PAGENUM=1 ID="BP63">Glossary</TITLE><GLOSSENTRY><GLOSSTERM>Bootstrap Protocol (BootP)</GLOSSTERM><GLOSSDEF><PARA>A standard means of supplying a computer on an IP network with its address and other configuration information when the computer is booted. BOOTP servers allow the network administrator to manage IP address assignment from a single location.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Domain</GLOSSTERM><GLOSSDEF><PARA>A group of networked computers under common DNS management. Domains can be determined by logical grouping rather than physical location.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Domain Name System (DNS)</GLOSSTERM><GLOSSDEF><PARA>A standardized system that provides information about hostname and IP address mapping throughout an internetwork. DNS maintains this information in a decentralized distributed database.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Domain SAP/RIP Server (DSS)</GLOSSTERM><GLOSSDEF><PARA>A service on a NetWare/IP<SUPERSCRIPT>TM</SUPERSCRIPT> network that replaces IPX<SUPERSCRIPT>TM</SUPERSCRIPT> broadcast services. DSS servers maintain a database that provides NetWare/IP servers and clients with SAP/RIP information (service availability and routing) required by NetWare« applications.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Driver</GLOSSTERM><GLOSSDEF><PARA>A software module that manages the operation of a specific device or protocol and provides services to modules running above it. Drivers allow higher-level modules, such as applications, to be device- and protocol-independent (able to run on any device or protocol for which a driver is available).</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Frame Type</GLOSSTERM><GLOSSDEF><PARA>Frame types determine how packets of network data are formatted on different LANs. Ethernet, token ring, ARCnet, and other LANs use different formats. The TCP/IP and IPX protocols also require different frame types in some instances.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Gateway</GLOSSTERM><GLOSSDEF><PARA>A system that transfers network data between different network types, translating the data between the two types as needed. For example, a NetWare/IP forwarding gateway passes NetWare traffic between IP and IPX segments, translating as needed between the two protocols.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Host</GLOSSTERM><GLOSSDEF><PARA>A networked computer.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Internetwork Packet eXchange<SUPERSCRIPT>TM</SUPERSCRIPT> (IPX)</GLOSSTERM><GLOSSDEF><PARA>A Novell communication protocol that sends data packets to requested destinations, such as servers and workstations. IPX addresses and routes outgoing data packets across a network. It reads the assigned addresses of incoming data and directs the data to the proper area of the workstation or server operating system.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Internet Protocol (IP)</GLOSSTERM><GLOSSDEF><PARA>An industry-standard suite of networking protocols that enables dissimilar nodes in a heterogeneous environment to communicate with one another.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>IP Router</GLOSSTERM><GLOSSDEF><PARA>A system that manages the exchange of information between TCP/IP networks. IP routers run special protocols that maintain information about the best way to transfer information among different networks, including hops across multiple networks.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>IPX Network Number</GLOSSTERM><GLOSSDEF><PARA>A hexadecimal number used by IPX to uniquely identify a network cable segment or a NetWare server. Each NetWare/IP domain, consisting of many servers and clients, is assigned a single IPX network number for communication with IPX resources.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Master DNS </GLOSSTERM><GLOSSDEF><PARA>The name server that maintains the read/write database of name-address mappings for an administrative zone (domain). Each zone has a single DNS master.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Name Server</GLOSSTERM><GLOSSDEF><PARA>A system that maintains a DNS database of hostname and IP address mappings. Name servers respond to queries from servers and client workstations for host addresses.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>NetWare/IP</GLOSSTERM><GLOSSDEF><PARA>A set of software modules that allows servers and workstations on TCP/IP networks to run NetWare. NetWare/IP replaces the traditional IPX transport with industry-standard TCP/IP, extends NetWare to TCP/IP networks, and can coexist with IPX NetWare.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>NetWare/IP Domain</GLOSSTERM><GLOSSDEF><PARA>A DNS domain used to administer NetWare/IP servers and clients. The NetWare/IP domain is always a subdomain that has no lower-level domains in the DNS hierarchy. </PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>NetWare DOS Requester<SUPERSCRIPT>TM</SUPERSCRIPT></GLOSSTERM><GLOSSDEF><PARA>The client software portion of NetWare 4. It replaces, and is compatible with, the NetWare shells used in previous NetWare versions.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Node</GLOSSTERM><GLOSSDEF><PARA>Any networked computer. Nodes include both server and client systems.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Parent Domain</GLOSSTERM><GLOSSDEF><PARA>The next higher level domain in the DNS hierarchy. For example, the parent domain of nwip.acme.com. is acme.com. Parent domains delegate administrative authority and responsibility to lower-level domains.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Port </GLOSSTERM><GLOSSDEF><PARA>In TCP/IP, a well-known point of access to a service on a host computer. Certain ranges of port numbers are usually assigned to the same services by convention; other ranges are available for use as needed by applications.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Primary DSS</GLOSSTERM><GLOSSDEF><PARA>The Domain SAP/RIP Server that maintains the global configuration information for a NetWare/IP network. One primary DSS is configured for each NetWare/IP domain.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Replica DNS </GLOSSTERM><GLOSSDEF><PARA>A name server that maintains a read-only copy of the DNS master's database for a domain. DNS replicas are configured to off-load network traffic from the master and to ensure service if the master becomes unavailable.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Routing Information Protocol (RIP)</GLOSSTERM><GLOSSDEF><PARA>An IPX protocol that propagates information about routes between nodes throughout an IPX internetwork.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Secondary DSS</GLOSSTERM><GLOSSDEF><PARA>An additional Domain SAP/RIP Server that supplements the primary DSS and off-loads NetWare/IP traffic from it. Secondary DSS servers are configured on remote subnetworks to provide service locally in case the primary DSS becomes unavailable.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Service Advertising Protocol (SAP)</GLOSSTERM><GLOSSDEF><PARA>An IPX protocol that propagates service availability information on a NetWare internetwork.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Transmission Control Protocol (TCP)</GLOSSTERM><GLOSSDEF><PARA>An industry-standard protocol that provides for reliable delivery of data over IP networks.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Unicode</GLOSSTERM><GLOSSDEF><PARA>An industry-standard 16-bit character representation scheme. Unicode allows you to represent the characters in multiple national languages using a single representation.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>User Datagram Protocol (UDP)</GLOSSTERM><GLOSSDEF><PARA>An industry-standard protocol that provides for unverified delivery of data over IP networks.</PARA>
</GLOSSDEF>
</GLOSSENTRY>
<GLOSSENTRY><GLOSSTERM>Virtual Loadable Module<SUPERSCRIPT>TM</SUPERSCRIPT> (VLM<SUPERSCRIPT>TM</SUPERSCRIPT>)</GLOSSTERM><GLOSSDEF><PARA>A modular executable program that runs at each NetWare workstation and enables communication with NetWare servers.These VLMs replace, and are compatible with, the NetWare shells used in previous NetWare versions. </PARA>
</GLOSSDEF>
</GLOSSENTRY>
</GLOSSARY>
</BOOK>